nestybox / nestybox/sysbox

Error while launching container inside of the SysBox System Container

Open
#630 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
3.9k
Forks
230
Avg merge
7h 48m
Merged PRs (30d)
3

Description

Hi Team,

I have been trying to deploy a System Container with Systemd, sshd, and Docker inside. Although I have been successfully able to deploy this system container. When I try to run my dockerized image(or any Docker Image for that matter), it returns me the following error:

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: mkdir /sys/fs/cgroup/rdma/docker: permission denied: unknown

Correct me if I am wrong but this error is being triggered because the SysBox Container does not have the necessary settings to modify the cgroup settings.

Another thing I would like to highlight here is that, I am testing out SysBox inside of a GCP VM and I am set to the Project Owner as well. So I believe spinning up the Container inside of a VM is not the cause of the issue here.

The VM OS Distribution is Ubuntu 18.04.6 LTS and I have checked that this Linux Distribution is supported by SysBox.

Your Help would be appreciated on this
Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report concerns Docker inside a SysBox system container on an Ubuntu 18.04.6 GCP VM, failing while creating the cgroup path /sys/fs/cgroup/rdma/docker. Start by reproducing the launch failure and tracing the cgroup configuration involved. Done means determining whether the permission error is expected and documenting a confirmed resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, gcp, ubuntu
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.