You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Charts visibility toggles for L1 and DRAM
- App navigation system
- Navigable operations in tensor list
- Docker CI/CD release integration
- Visualizer wheel release
- Buffer focus mode plot data order dependency fix
- Fix for null device operations
- Visual improvements
Copy file name to clipboardExpand all lines: .github/workflows/docker-image.yml
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,7 @@ name: Create and publish a Docker image
2
2
3
3
on:
4
4
push:
5
-
branches: [ "main", "dev" ]
6
-
tags:
7
-
- 'v*'
5
+
branches: [ "main" ]
8
6
9
7
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
Copy file name to clipboardExpand all lines: README.md
+82-74Lines changed: 82 additions & 74 deletions
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,83 @@
1
-
# React + TypeScript + Vite
1
+
# TTNN Visualizer
2
+
3
+
A tool for visualizing the Tenstorrent Neural Network (TTNN) model.
4
+
5
+
## Running Application
6
+
7
+
### Downloading Docker Image
8
+
9
+
Before executing the command below please see the note on SSH agent configuration.
10
+
11
+
In order to pull the image from ghcr.io you need to create an authentication token that allows you to "read:packages".
12
+
To create and use the token follow the instructions found [here](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic) .
13
+
14
+
After following the instructions above you should be able to pull the image by running the following command:
# If using a VPN to connect to remote machines remove ports
47
+
# and use the host network
48
+
# network: host
49
+
environment:
50
+
- SSH_AUTH_SOCK=/ssh-agent
51
+
volumes:
52
+
# Directory/volume for stored report data
53
+
- ./data:/app/backend/data
54
+
# Linux configuration
55
+
# - ${SSH_AUTH_SOCK}:/ssh-agent
56
+
# MacOS configuration
57
+
- /run/host-services/ssh-auth.sock:/ssh-agent
58
+
59
+
```
60
+
61
+
### SSH
62
+
63
+
To avoid exposing private keys in the docker image an ssh-agent is required to be running on the host machine. The agent
64
+
socket is then mounted to the guest container. For instructions on setting up your ssh-agent
65
+
see [this article](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?platform=windows#adding-your-ssh-key-to-the-ssh-agent)
66
+
67
+
Ensure that you are able to connect to the remote machine in question using your local ssh-agent (or the ssh-agent of the remote machine).
68
+
69
+
To view your currently available keys, `ssh-add -L`.
70
+
71
+
The docker-compose file should expand the parameter for your agent socket - you can confirm/see this value by entering `echo $SSH_AUTH_SOCK`.
72
+
The printed value should be the location of your SSH agent socket.
73
+
74
+
For MacOS you need to use the 'magic' socket file. The docker-compose.yml file has a volume mapping that points to this magic file, ensure that it is being used rather than `SSH_AUTH_SOCK`.
75
+
76
+
Before running the application ensure that your keys are added to the agent (`ssh-add -L`). If your keys are not present, run `ssh-add` to add them.
77
+
78
+
# Contributing
79
+
80
+
## React + TypeScript + Vite
2
81
3
82
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Before executing the command below please see the note on SSH agent configuration.
112
-
113
-
In order to pull the image from ghcr.io you need to create an authentication token that allows you to "read:packages".
114
-
To create and use the token follow the instructions found [here](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic) .
115
-
116
-
_Developer Note_
117
-
118
-
Available image versions can be found [here](https://github.com/tenstorrent/ttnn-visualizer/pkgs/container/ttnn-visualizer).
119
-
120
-
#### Docker Volumes
121
-
122
-
In order to avoid having to re-download reports when re-creating the image it is recommended to create a volume to store the report data. A volume can be created using the docker volume command, `docker volume create report-data`. This volume should be mounted in the container at `/app/backend/data`.
# If using a VPN to connect to remote machines remove ports
143
-
# and use the host network
144
-
# network: host
145
-
environment:
146
-
- SSH_AUTH_SOCK=/run/host-services/ssh-auth.sock
147
-
volumes:
148
-
# Volume for report data
149
-
- report-data:/app/backend/data
150
-
# Linux configuration
151
-
- ${SSH_AUTH_SOCK}:/ssh-agent
152
-
# MacOS configuration
153
-
# - /run/host-services/ssh-auth.sock:/ssh-agent
154
-
155
-
volumes:
156
-
report-data:
157
-
```
158
-
159
-
### SSH
160
-
161
-
To avoid exposing private keys in the docker image an ssh-agent is required to be running on the host machine. The agent
162
-
socket is then mounted to the guest container. For instructions on setting up your ssh-agent
163
-
see [this article](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?platform=windows#adding-your-ssh-key-to-the-ssh-agent)
164
-
165
-
Ensure that you are able to connect to the remote machine in question using your local ssh-agent (or the ssh-agent of the remote machine).
166
-
167
-
To view your currently available keys, `ssh-add -L`.
168
-
169
-
The docker-compose file should expand the parameter for your agent socket - you can confirm/see this value by entering `echo $SSH_AUTH_SOCK`.
170
-
The printed value should be the location of your SSH agent socket.
171
-
172
-
For MacOS you need to use the 'magic' socket file. The docker-compose.yml file has a volume mapping that points to this magic file, ensure that it is being used rather than `SSH_AUTH_SOCK`.
173
-
174
-
Before running the application ensure that your keys are added to the agent (`ssh-add -L`). If your keys are not present, run `ssh-add` to add them.
175
-
176
185
### Running project
177
186
178
-
To run the application you can simply run `docker-compose up web`. To rebuild add the build flag, `docker-compose up web --build`.
187
+
To run the application you can simply run `docker-compose up web`. To rebuild add the build flag, `docker-compose up web --build`.
179
188
180
189
To use the [provided SSH container](./docker/SSH/README.md) with the compose configuration you can substitute `web` in the above commands for `ssh`. To run the container in the background use `docker-compose up ssh -d`
181
190
182
-
To connect to this container through the remote connection manager you use the name of the service (`ssh`) as the 'host' and the default SSH port 22.
183
-
191
+
To connect to this container through the remote connection manager you use the name of the service (`ssh`) as the 'host' and the default SSH port 22.
0 commit comments