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
Debian Stretch
Root partition is a rootfs (ramdisk)
$ df -h /
Filesystem Size Used Avail Use% Mounted on
rootfs 63G 4.5G 59G 8% /
Issue
Any job using the exec driver fails to start which I believe because pivot_root does not work when the root partition is a ramdisk, see man 2 pivot_root
The rootfs (initial ramfs) cannot be pivot_root()ed.
I think Docker addressed this issue with the DOCKER_RAMDISK env variable which essentially disables pivot_root. I think what I need here is a way to disable pivot_root, probably as a configuration variable in the exec driver.
Hi @th0m! Thanks for opening this issue. I'm really curious to hear what you're doing with Nomad that you're running it from a rootfs!
As far as the feature request goes, that sounds reasonable. It looks like the underlying runc library supports this with the Config.NoPivot root field, so it'd be a matter of adding the config value to the exec stanza and then plumbing it through to runc. We'd love to get this as a contribution if you're interested.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Nomad v0.10.2
Operating system and Environment details
Debian Stretch
Root partition is a rootfs (ramdisk)
Issue
Any job using the
exec
driver fails to start which I believe becausepivot_root
does not work when the root partition is a ramdisk, seeman 2 pivot_root
I think Docker addressed this issue with the
DOCKER_RAMDISK
env variable which essentially disablespivot_root
. I think what I need here is a way to disablepivot_root
, probably as a configuration variable in theexec
driver.Reproduction steps
exec
driverJob file (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: