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
At work, we use CoreOS's Fleet to schedule our containers across a few servers. Interaction with Fleet is via a unix socket /var/run/fleet.sock. I would like to build a standard Docker bundle to list, start, and stop units. To do that, I'll need the Relay to send the mount option to the container. I imagine a slight change to the config.yaml as follows.
binds is a list of strings you would pass as values in HostConfig -> Binds in the POST body for the Docker /containers/create API endpoint
The relevant bit of that documentation for our purposes is quoted here:
host_path:container_path to bind-mount a host path into the container host_path:container_path:ro to make the bind-mount read-only inside the container. volume_name:container_path to bind-mount a volume managed by a volume plugin into the container. volume_name:container_path:ro to make the bind mount read-only inside the container.
At work, we use CoreOS's Fleet to schedule our containers across a few servers. Interaction with Fleet is via a unix socket
/var/run/fleet.sock
. I would like to build a standard Docker bundle to list, start, and stop units. To do that, I'll need the Relay to send the mount option to the container. I imagine a slight change to theconfig.yaml
as follows.Current:
Proposed:
The text was updated successfully, but these errors were encountered: