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
{{ message }}
This repository has been archived by the owner on Jul 10, 2023. It is now read-only.
I was unable to get Tango working out of the box. After quite a bit of debugging and digging I found the changes I made below worked, although they are fairly hacky.
The Tango vmms/localDocker.py requires you to mount /var/run/docker.sock to the docker container so it can use the docker command on the host (rather unsafe though). Furthermore, the autograding_image seems to mount /opt/TangoService/Tango/volumes, however, this image is run on the host and the path is for the container. This can be "fixed" by creating the directory /opt/TangoService/Tango/volumes and mounting it on the container. This can by modifying the docker-compose.yaml to be the following (the part about volumes):
@bobbens
I was able to get Tango working with a custom image but loggininto a running tango container (e.g. docker exec -it local_tango_1 bash) and pulling my own image inside it. So, i.t's docker inside docker, but hey, it works. don't forget to commit container changes to the image.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was unable to get Tango working out of the box. After quite a bit of debugging and digging I found the changes I made below worked, although they are fairly hacky.
The Tango vmms/localDocker.py requires you to mount /var/run/docker.sock to the docker container so it can use the docker command on the host (rather unsafe though). Furthermore, the
autograding_image
seems to mount/opt/TangoService/Tango/volumes
, however, this image is run on the host and the path is for the container. This can be "fixed" by creating the directory/opt/TangoService/Tango/volumes
and mounting it on the container. This can by modifying the docker-compose.yaml to be the following (the part about volumes):I would like to know if I am overlooking anything or if there is a more simple way to handle this.
The text was updated successfully, but these errors were encountered: