-
Notifications
You must be signed in to change notification settings - Fork 38
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
Creating Container failed #101
Comments
I can reproduce the problem at least. Let me see if can fix it and push an updated image. |
Thank very much ! |
A possible (not ideal) workaround for now would be to run the container in privileged mode. E.g with the |
ok, i will try. |
Unfortunately, I am a newbie in this field. I get the following error message when I download the image from the repository and run the run command with --privileged: Unable to find image 'privileged:latest' locally The run command is: docker run -d --name atom |
In your example, you have some extra space between |
oh sorry, i didn't see that. Now I can create the image. The futex facility returned an unexpected error code. /usr/bin/atom: line 192: 17 Aborted "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" |
For me it's working in privileged mode.... One thing to check, is the permissions on your host machine for the The owner should be your local user. If the owner shows as |
I have now given the .atom directory all permissions (under Windows10) and started the RUN command with the --privileged parameter. Now I get the message again: The futex facility returned an unexpected error code. /usr/bin/atom: line 192: 17 Aborted "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" |
Ok - then I guess it's not an issue with permissions. I don't use Windows or Docker Desktop so it's hard for me to figure out what's wrong for you. The actual issue is that by default the container does not have permission to the One other thing to try is adding |
Same behavior with |
Hello, This feature is available only if Docker has been built with seccomp and the kernel is configured with CONFIG_SECCOMP enabled. To check if your kernel supports seccomp:
Is enabled for the container seccomp? Unfortunately I can't check this because the container is not running. |
That command is meant for running on the host machine, not the container. I guess for Docker Desktop on Windows the Docker host is actually a Linux VM. Presumably it can support seccomp.... |
Hello,
when launching the image I get the following error message in Docker desktop:
The futex facility returned an unexpected error code.
/usr/bin/atom: line 192: 16 Aborted "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@"
what can I do?
The text was updated successfully, but these errors were encountered: