-
Notifications
You must be signed in to change notification settings - Fork 2
SW Installation
Please, install the docker image we provide for the training (see below).
This is methodologically relevant as we aim to maximize the effectiveness of training hours by focusing on the content of the course rather than spending time troubleshooting installation snags that may arise along the way.
By contrast, if you want to install the software yourself, you can browse our official 🌐 manual. At any rate, to customize the installation to the specific needs of the training, you ought to inspect the steps in the docker recipe and apply the required options.
To run the docker container, go through the following steps:
- Make sure that you have installed Docker correctly for your platform.
- Pull the docker image:
Tags older than
docker pull ghcr.io/icub-training/sandbox:latest
latest
are available at the sandbox versions page. - Launch the container:
where
docker run -it -p 6080:6080 --name <container_name> ghcr.io/icub-training/sandbox:latest
container_name
is an optional id that the user can specify to ease the later identification of the container. - From within the container shell, launch the following scripts:
start-vnc-session.sh
- Open up the browser on your host and connect to
localhost:6080
to get to the workspace desktop GUI.You should get the outcome below 🎉
Once done with the container, you can stop it in two different ways:
- Log out from the container shell straight away by pressing CTRL+D.
- Resorting to the docker command:
docker stop <container_name>
docker start <container_name>
docker attach <container_name>
docker container rm <container_name>
docker container ls -a
To permanently apply to a new image the changes you made to the docker container, you need to:
- Stop the container.
- Commit the changes to a new image:
docker commit <container_name> <image_name>
docker system prune -a
- Stick to standard terminals (opened via
docker attach <container_name>
or via the terminal in VNC) when launching docker commands. We spotted problems when dealing with terminals opened up from within the Docker GUI in Windows. - If the graphical interface of the container stops somehow working, just start it over by launching again the following command:
start-vnc-session.sh
Test whether the following tutorial runs as expected.
- From the docker desktop GUI, open up a shell.
- Within the shell terminal, type in the following:
⚠ Copy-paste does not work from the host to the docker desktop GUI. To get around this, simply browse this web page from within the docker desktop straight away: this time, copy-paste will work!
git clone https://github.com/vvv-school/tutorial_cartesian-interface.git cd tutorial_cartesian-interface/smoke-test ./test.sh
You should get the outcome below 🎉 |
---|
You may consider relying on the Gitpod Cloud IDE as infrastructure to run the docker image on the cloud:
- Use your GitHub credentials to sign up for Gitpod. You will have 50 hours/month free on public and private repositories.
- Visit the Gitpod Integrations and make sure that all GitHub options are ticked in.
- Install the Gitpod browser extension.
- Learn how to deal with our Gitpod-enabled repositories.
- Browse the hands-on repositories and try out Gitpod.
Should you experience any problem, don't hesitate to contact us by posting to our 👋 Q&A system.
Return to Home Page