Closed Alexhuszagh closed 1 year ago
I was not able to reproduce this problem. I ran
docker run -it --rm --security-opt seccomp=C:/Users/nick/profile.json ubuntu:20.04 bash
in Windows powershell, and it successfully gave me a shell.
A couple clarifying questions:
docker version
?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 30 days.
Prevent issues from auto-closing with a /lifecycle frozen
comment.
/lifecycle stale
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked
Actual behavior:
If running a docker command with a custom seccomp profile, and it reads the JSON profile as if it was the filename. An example (with the seccomp profile pasted below) is provided in steps to reproduce the behavior below. Expected behavior
It should load the seccomp profile from the filename after passing, rather than open and read the contents, and then assume this is the profile filename. This works differently than Docker on WSL2, Docker on Linux, and Podman. I'm using the default Ubuntu 20.04 image, to show the image doesn't matter.
Information:
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
Diagnostics Ouput:
Steps to reproduce the behavior:
The command:
seccomp profile:
If I try a much smaller profile, I get:
If I try just
"C:/Users/ahusz/git/cross/src/seccomp.json"
in the JSON file, I get:If I try to use backslashes for native Windows paths, I get errors about invalid escape characters, even if the baskslashes are properly escaped. In short, I can't even use a wrapper file to load the profile.``