Expected behavior

Volumes defined at the cmdline with -v should live during all run/session. The normal behavior and operation from a regular Ubuntu installation is to have a successful execution (exit code 0) from the pipeline detailed below in “Steps to reproduce this behavior”.

Actual behavior

Volumes flapping between start and stop states leave the container without access to those shared resources:

It’s also possible that since you reported this the underlying issue has been fixed in a subsequent beta release. If you could check again and let us know if the issue appears to be fixed, that would be great.