3

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
  • 34,778
  • 18
  • 87
  • 102

3 Answers3

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,061
  • 1
  • 33
  • 36
1

I solved it by setting:

sysctl -w user.max_user_namespaces=15000
Piero
  • 1,028
  • 7
  • 8
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
  • 34,778
  • 18
  • 87
  • 102