4

My Docker container will not start. The error message in the log is:

{"message":"OCI runtime create failed: container_linux.go:349: starting container process caused \
"process_linux.go:319: getting the final child's pid from pipe caused \\\"EOF\\\"\": unknown"}

What is next step?

cssyphus
  • 37,875
  • 18
  • 96
  • 111

5 Answers5

3

I solved it by setting:

sysctl -w user.max_user_namespaces=15000
Piero
  • 1,583
  • 10
  • 12
2

When using kubernetes, this error can be caused by a wrong memory notation in deployment settings.

Wrong

...
spec:
  template:
    spec:
      container:
        resources:
          limits:
            memory: "300m"
          requests:
            memory: "300m"

Fixed:

...
spec:
  template:
    spec:
      container:
        resources:
          limits:
            memory: "300Mi"
          requests:
            memory: "300Mi"
ton
  • 3,827
  • 1
  • 42
  • 40
0

Update 2021:

New answers in the below-linked thread assert that they have found solutions. See this answer, for example.

Original Answer:

This is a known feature.{1}

The solution that worked for me was to restart the server instance.

In Plesk:

  1. Tools & Settings (from side menu)

  2. Server Management (2nd grouping on left side)

  3. click on Restart Server

Reference:

https://github.com/moby/moby/issues/40835

cssyphus
  • 37,875
  • 18
  • 96
  • 111
0

For CentOS users, setting max_user_namespaces can be done as follows.
echo 15000 > /proc/sys/user/max_user_namespaces https://superuser.com/a/1294246/1640737

SKO
  • 32
  • 5
0

I solve it by upgrade the linux kernel from 4.15.0-202-generic to 4.15.0-206-generic #217-Ubuntu.

My docker --version is 20.10.17, build 100c701.

  • 1, install the newest kernel: sudo apt-get install -y linux-image-generic
  • 2, reboot the server

Tips: check your environment will be suitable for the newest kernel before install it !

Victor Lee
  • 2,467
  • 3
  • 19
  • 37