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

Issue launching sysbox-ce containers with docker-ce 20.10.13~3-0~debian-bullseye #503

Closed
struanb opened this issue Mar 11, 2022 · 3 comments
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@struanb
Copy link

struanb commented Mar 11, 2022

I'm experiencing a persistent error attempting to launch sysbox containers with the Docker docker-ce package version 20.10.13~3-0~debian-bullseye, obtainer from Docker's Debian Apt repo (https://download.docker.com/linux/debian/dists/bullseye/pool/stable/amd64/).

root@demo-worker-p549:~/.dockside/bin# docker run --rm -it --entrypoint=/bin/bash --runtime=sysbox-runc debian
Unable to find image 'debian:latest' locally
latest: Pulling from library/debian
e4d61adff207: Pull complete 
Digest: sha256:10b622c6cf6daa0a295be74c0e412ed20e10f91ae4c6f3ce6ff0c9c04f77cbf6
Status: Downloaded newer image for debian:latest
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:393: starting container process caused: process_linux.go:607: container init caused: write sysctl key net.ipv4.ping_group_range: write /proc/sys/net/ipv4/ping_group_range: invalid argument: unknown.

Reverting to docker-ce version 20.10.12~3-0~debian-bullseye is sufficient to workaround the issue.

@rodnymolina
Copy link
Member

@struanb, thanks for reporting this. At first glance looks like this is a dup of issue #502 just reported today. We are looking into it.

@rodnymolina rodnymolina added bug Something isn't working duplicate This issue or pull request already exists labels Mar 11, 2022
@struanb
Copy link
Author

struanb commented Mar 11, 2022

So it does. Sorry for not checking, the issue wasn't raised when I found the issue this morning. Thanks for looking into it.

@rodnymolina rodnymolina self-assigned this Mar 11, 2022
@rodnymolina
Copy link
Member

Not a problem at all @struanb. Will close this one as duplicated now. Btw, check my answer in the original issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants