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
Copy file name to clipboardExpand all lines: README.md
+30-26Lines changed: 30 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,52 +8,56 @@ A `development container` (or dev container for short) allows you to use a cont
8
8
<summary> Details of the services in this container </summary>
9
9
10
10
- ROS1 noetic with a base workspace `/home/ubuntu/ros_ws/`;
11
+
- Support for arm64 (jetson orin nano) and amd64 architectures;
12
+
- Support for NVIDIA Docker runtime for linux hosts;
11
13
- VNC server that allows direct browser access (http://localhost:3080/), so nothing is required to install and use it;
12
-
- A `ssh` server, to allow direct access from outside (`ssh ubuntu@localhost -p 3022`)
13
-
- A web `vscode` server for easy remote access when deploying it on the robot (http://localhost:3081/)
14
-
- Automatic `xcode +` command executed on each attachment for local X forwarding
14
+
- A `ssh` server, to allow direct access from outside (`ssh ubuntu@localhost -p 3022`);
15
+
- A web `vscode` server for easy remote access when deploying it on the robot (http://localhost:3081/);
16
+
- Automatic `xcode +` command executed on each attachment for local X forwarding;
15
17
- Custom environment and VScode configurations:
16
-
- Open split terminals on launch
17
-
- Setup all environments variables automatically for running ROS
18
-
- Automatically open the VNC interface in a ROS tab
19
-
- Custom .vscode tasks to deploy roscore/rviz
20
-
- Custom PS1 (terminal shell)
18
+
- Open split terminals on launch;
19
+
- Setup all environments variables automatically for running ROS;
20
+
- Automatically open the VNC interface in a ROS tab;
21
+
- Custom .vscode tasks to deploy roscore/rviz;
22
+
- Custom PS1 (terminal shell);
21
23
</details>
22
24
23
-
## Quick usage
24
-
25
-
- VNC: http://localhost:3080
26
-
- VScode: http://localhost:3081
27
-
- SSH: `ssh ubuntu@localhost -p 3022`
28
-
- user: `ubuntu`
29
-
- pass: `ubuntu`
30
-
31
-
<figure>
32
-
<imgsrc="https://github.com/user-attachments/assets/6c085018-0b43-4f0e-9316-20bac5d0d4c1"alt="Fully loaded interface with the VNC client and multiple terminals on the bottom panel"style="width:100%">
33
-
<figcaption>Fully loaded interface with the VNC client and multiple terminals on the bottom panel.</figcaption>
34
-
</figure>
25
+
## Devcontainers installation
35
26
36
-
## Installation
27
+
- Open folder with VScode using the dev containers plugin (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
37
28
38
-
Open folder with VScode using the dev containers plugin (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
29
+
## Quick usage
39
30
40
-
##Build directy with 'docker compose'
31
+
### Start devcontainer on VScode or use `docker compose`
41
32
42
-
When the host is a linux-based machine:
33
+
-When the host is a linux-based machine:
43
34
```
44
35
BUILDKIT_PROGRESS=plain docker compose -f compose_linux_host.yaml up --build
45
36
```
46
37
47
-
When the host is a macos-based machine:
38
+
-When the host is a macos-based machine:
48
39
```
49
40
BUILDKIT_PROGRESS=plain docker compose -f compose_macos_host.yaml up --build
50
41
```
51
42
52
43
`BUILDKIT_PROGRESS=plain` helps to visualize step by step output of each of the commands.
53
44
45
+
### Usage
46
+
47
+
- VNC: http://localhost:3080
48
+
- VScode: http://localhost:3081
49
+
- SSH: `ssh ubuntu@localhost -p 3022`
50
+
- user: `ubuntu`
51
+
- pass: `ubuntu`
52
+
53
+
<figure>
54
+
<imgsrc="https://github.com/user-attachments/assets/6c085018-0b43-4f0e-9316-20bac5d0d4c1"alt="Fully loaded interface with the VNC client and multiple terminals on the bottom panel"style="width:50%">
55
+
<figcaption>Fully loaded interface with the VNC client and multiple terminals on the bottom panel.</figcaption>
56
+
</figure>
57
+
54
58
## Know issues
55
59
56
-
- The website preview does open a terminal with a extrange cannot find shell for command XXXX.
60
+
- The live preview opens a terminal with a message "cannot find shell for command XXXX". This can be safely ignored.
57
61
- The live preview will show a small box with a message "Please reopen the preview". This is fixed in the newest version of the live preview plugin.
0 commit comments