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
{{ message }}
This repository has been archived by the owner on Apr 17, 2021. It is now read-only.
The present solutions manually create bindpoints inside the image and rely upon a startup CMD that mounts them one-by-one at container instantiation. A better solutions would be to use autofs. This will require the use of a container service solution like supervisord or dumb-init. Solution will more or less get rid of /etc/fstab and replace mount -a with the invocation of autofs.
The text was updated successfully, but these errors were encountered:
P.S. I have vague memories that autofs inside a container on MacOS basically doesn't work because it's limited in fundamental ways by volume mounting in MacOS itself. A use case to test.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The present solutions manually create bindpoints inside the image and rely upon a startup CMD that mounts them one-by-one at container instantiation. A better solutions would be to use
autofs
. This will require the use of a container service solution likesupervisord
ordumb-init
. Solution will more or less get rid of/etc/fstab
and replacemount -a
with the invocation ofautofs
.The text was updated successfully, but these errors were encountered: