0

I am facing "exit status 34" while creating docker service. please suggest what is the issue.

Docker version : Docker version 17.09.1-ce, build 19e2cf6 Error Log :nsenter: failed to unshare namespaces: Cannot allocate memory container_linux.go:265: starting container process caused "process_linux.go:270: running exec setns process for init caused \"exit status 34\"" ERROR: Service 'web' failed to build: oci runtime error: container_linux.go:265: starting container process caused "process_linux.go:270: running exec setns process for init caused \"exit status 34\""

  • "Cannot allocate memory" - do you have enough memory for whatever you are trying to do? – jordanm Jan 25 '18 at 14:18
  • Have you tried to create more than 1023 containers? – Michael Hampton Jan 25 '18 at 16:22
0

I'm facing this issue too.

Here what I did find:

I have a situation where the client reports that the hosts was running and after some unknown update it stop working. I'm still looking for a coherent explanation. I'll update when fix it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.