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

wish: define how relative paths are handled for seccomp= #8749

Open
markstos opened this issue May 1, 2019 · 3 comments
Open

wish: define how relative paths are handled for seccomp= #8749

markstos opened this issue May 1, 2019 · 3 comments
Labels
area/engine Issue affects Docker engine/daemon lifecycle/frozen

Comments

@markstos
Copy link

markstos commented May 1, 2019

Regarding File: engine/security/seccomp.md

  • I'm getting a "file not found" when trying to set a seccomp profile in a Jenkins environment. The environment is dynamic, so it's not clear what a correct absolute path value would be. The current documentation makes no mention of how relative paths paths are resolved for seccomp, or if they are supported at all.
@traci-morrison traci-morrison added the area/engine Issue affects Docker engine/daemon label Dec 10, 2019
@docker-robott
Copy link
Collaborator

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

@docker-robott
Copy link
Collaborator

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

@docker-robott
Copy link
Collaborator

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/engine Issue affects Docker engine/daemon lifecycle/frozen
Projects
None yet
Development

No branches or pull requests

3 participants