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
I'm having a problem using docker-compose in the container though. When I run docker-compose up it works up until the point I try to use a volume. The volume has a path like /docker/overlay2/487580445a3dc1d1231e74ea5b7fd782343905c69fcb796543906f6c75699784/merged but the merged folder does not exist.
Well it does exist but only on the docker host where It's mounted as an overlay FS. It seems the container is not able to access the data even if I manually mount the docker datadir to the runner container.
Anyone had this happening or knows a way around the overlay filesystem?
The text was updated successfully, but these errors were encountered:
Thanks for this slick repository!
I'm having a problem using docker-compose in the container though. When I run docker-compose up it works up until the point I try to use a volume. The volume has a path like
/docker/overlay2/487580445a3dc1d1231e74ea5b7fd782343905c69fcb796543906f6c75699784/merged
but the merged folder does not exist.Well it does exist but only on the docker host where It's mounted as an overlay FS. It seems the container is not able to access the data even if I manually mount the docker datadir to the runner container.
Anyone had this happening or knows a way around the overlay filesystem?
The text was updated successfully, but these errors were encountered: