How to fix OCI runtime create failed in Docker

Related searches

I imported a Docker image on my new Rasbian Stretch installation. The image run good on the previous installation (Rasbian Stretch too). The problem is : when i try to run image on the new installation with bash command (but laso with npm start, etc), i have this problem :

$ docker run -ti nodejs:latest bash
docker: Error response from daemon: OCI runtime create failed:    container_linux.go:345: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown.

I try to save again the original image to do again the import and run. But it's always the same problem.

The docker version on the previous installation is : 18.04.0-ce And now: 18.09.0.

I try to install the same version of docker than before but it didn't change anything.

I also try this solution : Which say to remove the line "MountFlags=slave" in /lib/systemd/system/docker.service But i don't have this file. So i did :

grep -sr "MountFlags=slave" /

Output :


so, I went to /lib/systemd/system/systemd-udevd.service to put in commentary the line "MountFlags=slave". Then I did : systemctl daemon-reload and systemctl restart docker

But noting work and I have still the same problem.

Finally this works : docker run hello-world

My Dockerfile :

    FROM node:8-jessie

RUN apt-get update
RUN apt-get install -y vim fswebcam 

# for mjpg_streamer
RUN apt-get install -y cmake libjpeg8-dev
RUN apt-get install -y gcc g++

CMD ['npm', 'start']

I don't understand why my image can't run on my new installation whereas it works on my previous installation.

Thanks you !

Just explicitly install bash in your Dockerfile. For example change this line in your Dockerfile:

RUN apt-get install -y vim fswebcam bash

Or Use the sh shell For example change this in your run command:

docker exec -ti nodejs:latest sh

How to fix OCI runtime create failed in Docker, docker: Error response from daemon: OCI runtime create failed: Same problem on docker-ce within jenkins container, running on Windows 10 host (inception): Docker OCI runtime create failed: container_linux.go:349: starting container process caused. I don’t know why all this happened and I wanted to fix it.

I know this is the old thread but putting the solution here that worked for me.

Instead of importing docker image using

docker load --input <dockeriamges.tar>

It worked for me.

docker: Error response from daemon: oci runtime error , I'm having a similar problem. My Error message is this: ERROR: for logstash Cannot start service logstash: OCI runtime create failed:� I have some troubles when I try to start my go application with docker. ERROR: for app Cannot start service app: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"./main\": permission denied": unknown It happenes when I try to do docker-compose up. It is my mulristage Dockerfil:

i found the "solution" -> I don't know why but I just re make the image with the dockerfile.

Error when trying to run docker-compose up. "oci runtime error , The Problem: In preparation to run VM's on our IBM SAN we attempted running Docker on a Proxmox container which was running Debian 9. I'm setting up ArchiveBox using the Docker image and instructions found here. Though it appears to have been successfully setup on my computer, I cannot use the main command to add an individual li

docker: Error response from daemon: OCI runtime create failed , 1: stop docker with systemctl stop docker 2: run docker in debug mode dockerd --debug 3: start container with docker start container_name Then check the output in docker debug console in 2. In my case, it shows

I'm using docker-compose for nginx service, here is the docker-compose.yml file: version: '3' networks: laravel: services: nginx: image: nginx:stable-alpine container_name: nginx

Thanks for the feedback :-) Yes, because the example-files are more like a "template" for everybody. So there are more environment variables to consider and the db-credentials are in a separated file.

  • Thanks for your answer, but i have the same problem with sh. And even if i install batch according to your fisrt command.
  • change docker run to docker exec please ;)