OCI runtime failed container_linux:345 starting container process caused process_linux init caused rootfs_linux:58 mounting caused perm deni unknown

Asked Aug 26 '19 at 18:02

Active Sep 08 '20 at 08:01

Viewed 2,132 times

I'm setting up Nakama for a personal Unity3D project.

Normally it has to return to a normal command-line. Like user@vps-24-nextwab:~$

I use Docker version 18.09.7, build 2d0083d

I tried on two different VPS, with a root and non-root user.

What I type:

sudo docker run --name=db -p 26257 -p 8080 cockroachdb/cockroach start --insecure

The output is:

docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"rootfs_linux.go:58: mounting \\"proc\\" to rootfs \\"/var/lib/docker/vfs/dir/7c1c7c17556e9d13882fb75c32952a72b3e25cfd9ce992958d6750b5e72bbc5e\\" at \\"/proc\\" caused \\"permission denied\\"\"": unknown.

edited Aug 26 '19 at 20:53

asked Aug 26 '19 at 18:02

Fruity Label

Seems pretty weird, and I could not reproduce it with Docker `19.03.1, build 74b1e89` on Ubuntu 18.04. Could you try fresh version of Docker? – Danila Kiver Aug 26 '19 at 19:56
This: `--name=db-p 26257 -p 8080` looks strange. Are you missing a space between `db` and `-p 26257`? If that's the case, please [edit] your question and provide the correct command line. – Frank Schmitt Aug 26 '19 at 20:37
I missed a space – Fruity Label Aug 26 '19 at 20:54
Nothing changed, same error. Thanks – Fruity Label Aug 26 '19 at 21:00
This looks like a problem with mounting/volumes. – RichArt Nov 28 '19 at 08:53
@FruityLabel were you using with lxc? – Alok Deshwal Sep 08 '20 at 08:01

OCI runtime failed container_linux:345 starting container process caused process_linux init caused rootfs_linux:58 mounting caused perm deni unknown

0 Answers0