-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Description
I'm trying to run busybox container in Colab, however I've got the following error:
WARN[0000] signal: killed
ERRO[0000] container_linux.go:349: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mkdir /sys/fs/cgroup/cpuset/container1: read-only file system\""
container_linux.go:349: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mkdir /sys/fs/cgroup/cpuset/container1: read-only file system\""
Here are the steps:
- Install Docker and runc:
%%shell
curl -s https://download.docker.com/linux/static/stable/x86_64/docker-19.03.9.tgz | tar vxz --strip=1 -C /usr/local/bin/
wget -cqO /usr/local/bin/runc https://github.com/opencontainers/runc/releases/download/v1.0.0-rc92/runc.amd64 && chmod +x /usr/local/bin/runc
docker --version
runc --version
- Extract Busybox container into
busybox/rootfs:
%%shell
dockerd -b none --iptables=0 -l warn &
sleep 1
mkdir -pv busybox/rootfs
docker export $(docker create busybox) | tar -C busybox/rootfs -xf -
kill $(jobs -p)
- Run:
%%shell
cd busybox
runc spec --rootless
runc run --no-new-keyring --no-pivot container1
Demo: https://colab.research.google.com/drive/19hVpEODrL8kb7KvyWrA9vE6Pd7ZKMA4G#scrollTo=VhgKc1a6zMTq
Is there any way to run the container having read-only access to cgroup configuration?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels