Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable host filesystem access by default #7210

Closed
7 of 8 tasks
schmichael opened this issue Feb 20, 2020 · 2 comments
Closed
7 of 8 tasks

Disable host filesystem access by default #7210

schmichael opened this issue Feb 20, 2020 · 2 comments

Comments

@schmichael
Copy link
Member

schmichael commented Feb 20, 2020

Since host volumes were introduced in Nomad v0.10, operators have a way to explicitly enable which host filesystem paths are accessible by allocations.

Any default behaviors or configurations which allow unrestricted host filesystem access should be disabled by default. The Nomad client agent's configuration must explicitly grant host filesystem access to allocations via host volumes or other explicit configuration parameters.

Task Driver Changes

  • docker.volumes.enabled should default to false
  • rkt.volumes.enabled should default to false -- also move rkt out of tree Deprecate rkt #6478
  • exec/java should already restrict paths to inside the chroot, but this restriction should be verified
  • qemu should restrict image paths to the allocation directory.
    • If Nomad v0.10 allowed qemu images to be loaded from any path, a client configuration parameter that whitelists host paths should be added (eg qemu.image_paths = ["/mnt/images"])
  • File issues with all community plugins that allow full filesystem access to disable it by default.
    • Lower priority since plugins are (a) outside our control and (b) must be enabled manually already
  • raw_exec is already disabled by default and therefore requires no changes

Other Changes

@stale

This comment has been minimized.

@github-actions
Copy link

github-actions bot commented Nov 5, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.