Whenever I need to reboot my machine for some reason, the containers created via the init script do not work anymore. Whether I try to restart the container with the provided go.sh script or simply by docker start [container_name], I get this sort of error message:
Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/tmp/.docker.xauth\\\" to rootfs \\\"/var/lib/docker/overlay2/959ab1b2a56015caa38a03b15c624dc997238c79c38cc5eb192974c21ee8560d/merged\\\" at \\\"/var/lib/docker/overlay2/959ab1b2a56015caa38a03b15c624dc997238c79c38cc5eb192974c21ee8560d/merged/tmp/.docker.xauth\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Error: failed to start containers: home-fbottarel-workspace-docker-ros-box-pcl-box
I am not familiar with the inner workings of Docker and the way it handles mounted volumes, hence I am not sure how to tackle this (or if this is even solvable). @pierrekilly is this nominal behaviour?
Whenever I need to reboot my machine for some reason, the containers created via the init script do not work anymore. Whether I try to restart the container with the provided
go.sh
script or simply bydocker start [container_name]
, I get this sort of error message:I am not familiar with the inner workings of Docker and the way it handles mounted volumes, hence I am not sure how to tackle this (or if this is even solvable). @pierrekilly is this nominal behaviour?