Starting container with both data volume container & host volume


I’m a bit new to using data volume containers for persistence and have normally used host volumes to store persistent data. However, I’ve since switched my host to RancherOS and am trying to avoid having to use host volumes wherever possible.

I’m trying to create a service which has a sidekick container to hold configuration data, but also add host-mounted volumes (to access an external mounted disk). It seems only the host-mounted volumes get mounted in the service container but when I try to “docker run --rm -ti ubuntu:14.04.3 /bin/bash” to examine the contents of the data volume container, I notice that the configuration data isn’t stored in the data volume container.

Anyone have any tips for a setup like this? Thanks!

1 Like