Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when trying to run docker-compose up. "oci runtime error: container_linux.go:247..." #4039

Closed
michalwarda opened this Issue Oct 18, 2016 · 64 comments

Comments

Projects
None yet
@michalwarda
Copy link

michalwarda commented Oct 18, 2016

When trying to launch a built container with docker-compose up I'm getting an error:

ERROR: for app  Cannot start service app: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"script/docker-entrypoint.sh\\\": stat script/docker-entrypoint.sh: no such file or directory\"\n"
ERROR: compose.cli.main.main: Encountered errors while bringing up the project.

I've tried reinstalling docker, docker-compose, virtualbox, rebuilding containers, recreating machines.
Downgrading almost all of those things to previous versions. Literally retrying the whole docker instalation flow.

The problem occurs only in docker-compose up. Everything works fine when I use docker run ....
The important thing is the whole setup works correctly on my OSX installation. Unfortunately my Xenial Ubuntu doesn't want to cooperate.

I've checked the issues archive and couldn't find an answer that would help me fix the problem.

Here are my whole setup configs:
docker-compose.yml:

version: "2"
services:
  app:
    build: .
    volumes:
      - .:/app
    depends_on:
      - cache-redis
    links:
      - cache-redis
  nginx:
    image: nginx:1.11.1-alpine
    depends_on:
      - app
    links:
      - app
    ports:
      - "80:80"
    volumes:
      - ./config/nginx/app.conf:/etc/nginx/conf.d/default.conf
  cache-redis:
    image: redis:3.2.1-alpine
    volumes:
      - cache-redis:/var/lib/cache-redis/data

volumes:
  cache-redis:
    driver: local

Dockerfile

FROM jruby:9.1.2.0-jre-alpine

RUN apk --update --no-cache add build-base less git openssh

RUN mkdir -p /app

WORKDIR /app

COPY Gemfile Gemfile.lock ./

RUN gem install bundler && bundle install

COPY . ./

CMD ["script/docker-entrypoint.sh"]

script/docker-entrypoint.sh

#!/bin/sh
rm -f tmp/pids/server.pid
padrino s -h 0.0.0.0

docker-compose -v:
docker-compose version 1.8.1, build 878cff1

docker version:

Client:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 18:29:41 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 17:00:50 2016
 OS/Arch:      linux/amd64

docker info:

Containers: 6
 Running: 1
 Paused: 0
 Stopped: 5
Images: 15
Server Version: 1.12.2
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 37
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.24-boot2docker
Operating System: Boot2Docker 1.12.2 (TCL 7.2); HEAD : 9d8e41b - Tue Oct 11 23:40:08 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.9 MiB
Name: default
ID: G442:OWMQ:BPXD:7MK5:HM7J:R7PO:DNBP:ZSKI:HJH4:OCE4:UX36:M2PO
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 21
 Goroutines: 38
 System Time: 2016-10-18T09:18:30.024046419Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Insecure Registries:
 127.0.0.0/8
@michalwarda

This comment has been minimized.

Copy link
Author

michalwarda commented Oct 18, 2016

I've managed to fix it. I had wrong permissions and needed to run docker-compose as sudo.

@jakerobers

This comment has been minimized.

Copy link

jakerobers commented Oct 24, 2016

I am getting this error too, and sudo fixed it. However, there should be an alternative solution to this issue.

@chrisdpeters

This comment has been minimized.

Copy link

chrisdpeters commented Nov 11, 2016

@michalwarda @jakerobers I am experiencing this issue too. I think you should reopen the issue.

I am using a pretty vanilla install of Docker for Mac, and I can't remember doing anything that would require this permission level on the docker-compose command.

@cloutiertyler

This comment has been minimized.

Copy link

cloutiertyler commented Nov 14, 2016

I'm getting a similar error and unfortunately sudo doesn't fix this one.

ERROR: for grafana  Cannot start service grafana: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"/init-grafana-and-run.sh\\\": permission denied\"\n"
@wojked

This comment has been minimized.

Copy link

wojked commented Nov 17, 2016

I had similar issue with my images and found this thread.
In my case, It turned out that mounting the volumes is the source of confusion.

In your case, please make sure that app.conf is an existing file.
./config/nginx/app.conf:/etc/nginx/conf.d/default.conf

This will mount your local app.conf inside of the docker container.
If it does not exist on your local machine, docker will create locally an "app.conf" directory, which is not what you would usually expect in this particular case.

I hope it will help you.

@artem-gavrylenko

This comment has been minimized.

Copy link

artem-gavrylenko commented Nov 17, 2016

click on icon tray Docker > Settings... > Shared Drivers and select checkbox Shared: C and D
Maybe it`s help you!

@danimbrogno

This comment has been minimized.

Copy link

danimbrogno commented Nov 23, 2016

I've noticed having a CMD line in a dockerfile and a -command parameter in a docker-compose file will also trigger this error.

@bitwombat

This comment has been minimized.

Copy link

bitwombat commented Dec 28, 2016

This issue shouldn't be closed - it still happens, and sudo isn't really a good solution when needing to point docker-compose at a remote machine for deployment.

This is with docker-compose 1.9.0.

Interestingly, if I ssh into the machine, docker-compose up -d completes without an error. So, for me, this only happens when running remotely.

Odd thing is, the mount in the error message is for a local path (in bold below) - referred to relatively in my docker-compose, so perhaps this is a relative/absolute path problem with docker-compose.

ERROR: for nginx Cannot start service nginx: invalid header field value "oci runtime error:
container_linux.go:247: starting container process caused "process_linux.go:359: container init caused
\"rootfs_linux.go:53: mounting \\\\ "/data/www/aq/docker/nginx/default.conf \\\" to rootfs \\\"/var
/lib/docker/aufs/mnt/8e3b80c25d85b70b78ea479a5f68373e236fdd3dafd62b241495907ace62da2f\\\"
at \\\"/var/lib/docker/aufs/mnt
/8e3b80c25d85b70b78ea479a5f68373e236fdd3dafd62b241495907ace62da2f/etc/nginx/conf.d
/default.conf\\\" caused \\\"not a directory\\\"\""\n"

This is due to a line in docker-compose.yml trying to point nginx's configuration back to the local filesystem:

    volumes:
      - ./docker/nginx/default.conf:/etc/nginx/conf.d/default.conf

This should resolve to /home/root/docker on the remote, and /data/www/aq/docker locally. Instead, docker-compose seems to be trying to use the local path on the remote.

Happy to provide any other details/logs.

gitsimon added a commit to tanzquotient/tq_website that referenced this issue Jan 6, 2017

clean/polish docker-compose files
dockerfile-new is still separated for reference
added memcached again and necessary links
added restart:always to all containers

still problems when trying to run a bash inside a container (e.g. for running collectstatic):
docker/compose#4039
@sajadghawami

This comment has been minimized.

Copy link

sajadghawami commented Jan 30, 2017

you gotta make the docker-entrypoint.sh an executable before building the image:

chmod +x docker-entrypoint.sh

otherwise it cant be executed and you get the permission error.

@augnustin

This comment has been minimized.

Copy link

augnustin commented Feb 8, 2017

Same issue here. No idea how it started yet.

@augnustin

This comment has been minimized.

Copy link

augnustin commented Feb 8, 2017

Found it, I was not assigning options in the right order:

docker-compose run web -f docker-compose-prod.yml /bin/bash

fails while:

docker-compose run -f docker-compose-prod.yml web /bin/bash

works.

Those parameter order restrictions are quite of annoying. Never has so many issues with any Unix executable...

@EAZYE9000

This comment has been minimized.

Copy link

EAZYE9000 commented Feb 16, 2017

Been bashing my head into my keyboard trying to get this to work. Thanks for posting the fix!

@imarchuang

This comment has been minimized.

Copy link

imarchuang commented Feb 22, 2017

This issue happens on my native docker on Mac too... no idea how to resolve it!

ERROR: for elasticsearch  Cannot start service elasticsearch: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/Users/mhuang/docker/elk/elasticsearch/config/elasticsearch.yml\\\" to rootfs \\\"/var/lib/docker/aufs/mnt/f41ff7a7a6fff5c6aa141ff8e9ca2d8c85740e4c7c707c6f720312703392b84a\\\" at \\\"/var/lib/docker/aufs/mnt/f41ff7a7a6fff5c6aa141ff8e9ca2d8c85740e4c7c707c6f720312703392b84a/usr/share/elasticsearch/config/elasticsearch.yml\\\" caused \\\"not a directory\\\"\""
: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

below are some info about my docker:

$ docker version
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      linux/amd64
 Experimental: true
$ docker info
Containers: 15
 Running: 0
 Paused: 0
 Stopped: 15
Images: 38
Server Version: 1.13.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 380
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.8-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.952 GiB
Name: moby
ID: 247X:LGNT:FJ4M:U6XE:T47E:WXLQ:VFXY:D3Z2:MBPI:KMAL:32LQ:DDHF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 17
 Goroutines: 27
 System Time: 2017-02-22T19:00:56.756261436Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
@sajadghawami

This comment has been minimized.

Copy link

sajadghawami commented Feb 23, 2017

@imarchuang your seems to be a different problem!

What are you trying to mount? Seems like a folder on your host doesnt exist.

Please provide your docker-compose file

@chielsen

This comment has been minimized.

Copy link

chielsen commented Feb 27, 2017

I'm having the same issues. I was running a php-fpm and nginx container.
Rebooted my windows machine, and it couldn't find the files anymore i was trying to include on the php-fpm container.

NOTICE: PHP message: PHP Warning:  Unknown: failed to open stream: No such file or directory in Unknown on line 0
172.17.0.5 -  27/Feb/2017:14:06:05 +0000 "GET /index.php" 200
NOTICE: PHP message: PHP Fatal error:  Unknown: Failed opening required '/var/www/xxxx/public/index.php' (include_path='.:/usr/share/php') in Unknown on line 0
172.17.0.5 -  27/Feb/2017:14:06:06 +0000 "GET /index.php" 404
ERROR: Unable to open primary script: /var/www/xxxx/public/index.php (No such file or directory)

Then restarted the container and got:

Cannot start service loanstreet-php-fpm: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/C/Web/Apache/htdocs/sxxxxxx/php-fpm/php-ini-overrides.ini\\\" to rootfs \\\"/var/lib/docker/aufs/mnt/83e56fa30d7fae9156dc5842b62f1bc65cbbbcbfebabd96bb4d3513df53458bc\\\" at \\\"/var/lib/docker/aufs/mnt/83e56fa30d7fae9156dc5842b62f1bc65cbbbcbfebabd96bb4d3513df53458bc/etc/php/7.1/fpm/conf.d/99-overrides.ini\\\" caused \\\"not a directory\\\"\""

@romaindequidt

This comment has been minimized.

Copy link

romaindequidt commented Feb 27, 2017

"volumes" binds directories... not files.

@imarchuang bind the "config" directory => elk/elasticsearch/config with /usr/share/elasticsearch/config

@chielsen bind "php-fpm" direcotry with /etc/php/7.1/fpm/conf.d directory

@imarchuang

This comment has been minimized.

Copy link

imarchuang commented Feb 27, 2017

@chielsen

This comment has been minimized.

Copy link

chielsen commented Feb 27, 2017

@romaindequidt That is weird since it always worked. I got this from https://phpdocker.io/generator
Mounting a file is also specified in here: https://docs.docker.com/engine/tutorials/dockervolumes/#mount-a-host-file-as-a-data-volume

I found a workaround for now, making the file readonly, adding ':ro' on the end of the line.

@sajadghawami

This comment has been minimized.

Copy link

sajadghawami commented Feb 27, 2017

You either mount a specific file, or you mount a whole folder.
You cannot mount a single file into a folder!

As taken from the link provided by @chielsen you can do this:

docker run --rm -it -v ~/.bash_history:/root/.bash_history ubuntu /bin/bash

which maps the users local .bash_history file into the container with the specified filename.

@skobkin

This comment has been minimized.

Copy link

skobkin commented Feb 28, 2017

I just caught this error after updating of docker without restarting docker daemon.

Step 9/13 : RUN /bin/ln -s /etc/nginx/sites-available/symfony.conf /etc/nginx/sites-enabled/symfony.conf
 ---> Running in ea68a8b4bf61
container_linux.go:247: starting container process caused "process_linux.go:334: running prestart hook 0 caused \"fork/exec /usr/bin/dockerd (deleted): no such file or directory\""
ERROR: Service 'nginx' failed to build: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:334: running prestart hook 0 caused \\\"fork/exec /usr/bin/dockerd (deleted): no such file or directory\\\"\"\n"

After restarting all works normal.

@otafasd

This comment has been minimized.

Copy link

otafasd commented Apr 13, 2017

In my case, I've changed docker-compose.yml file.
from
- /usr/local/bin/docker:/usr/bin/docker
to
- /usr/bin/docker:/usr/bin/docker

It works fine.

@chielsen

This comment has been minimized.

Copy link

chielsen commented May 16, 2017

I still occasionally have this error. I actually just bought a new pc and did a clean win 10 install and still have this issue. Only way to fix it is to reboot.
Is anybody looking into this?

@skobkin

This comment has been minimized.

Copy link

skobkin commented May 18, 2017

@chielsen Seems like it may happen at least after Docker update. I solved this problem for me with restarting Docker daemon.

@minchangchen

This comment has been minimized.

Copy link

minchangchen commented May 24, 2017

when i docker run , i get following error
Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"chdir to cwd (\\\"/data/env/tomcats/0\\\") set in config.json failed: no such file or directory\"\n" Error: failed to start containers: fd2e03516c08
and my dockerfile in following
`FROM minchangchen/openjdk:latest
MAINTAINER minchangchen
LABEL name="tomcat" license="MIT" build-date="20170223"

ENV VERSION 8.5.15
ENV TOMCAT_PATH /data/env/tomcats/0

RUN yum update -y && cd /data/softs && wget http://www-us.apache.org/dist/tomcat/tomcat-8/v$VERSION/bin/apache-tomcat-$VERSION.tar.gz && tar -zxf apache-tomcat-$VERSION.tar.gz && mkdir /data/env/tomcats && mv apache-tomcat-$VERSION $TOMCAT_PATH && rm -rf /data/softs/*

COPY catalina.sh $TOMCAT_PATH/bin/catalina.sh
COPY server.xml $TOMCAT_PATH/conf/server.xml
COPY context.xml $TOMCAT_PATH/conf/context.xml

RUN chmod +x $TOMCAT_PATH/bin/catalina.sh

WORKDIR $TOMCAT_PATH

CMD ["bin/catalina.sh", "run"]`

everybody help me !!! - . --

@objectivePinta

This comment has been minimized.

Copy link

objectivePinta commented May 29, 2017

This is happening with docker-toolbox on windows 7 as well:

ERROR: for storage_startup  Cannot start service storage_startup: invalid header
 field value "oci runtime error: container_linux.go:247: 
starting container process caused \"exec: \\\"./startup.sh\\\":
 permission denied\"\n"
@SamAyoub

This comment has been minimized.

Copy link

SamAyoub commented Jun 8, 2017

objectivePinta Try to restart your toolbox when you get this error. and restart your container,
if you still have the same error, just use the virtual box in docker toolbox and then return to the normal one and it should fix it.

@veqryn

This comment has been minimized.

Copy link

veqryn commented Jun 16, 2017

Got this today.
Windows 10 Pro with the Docker App (native hyper-v) 17.03.1-ce-win5 (10743)
I've been running this particular container for months now without issue. Restarted laptop and the bug hasn't returned.

ERROR: for goconvey-dev  Cannot start service goconvey-dev: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/C/Users/xxx/workspace/go/src/github.com/xxx\\\" to rootfs \\\"/var/lib/docker/overlay2/c39c054c44d82f699180b40c19a5a626c74063f8c9defa0c2a2bf12dfdb7972d/merged\\\" at \\\"/go/src/github.com/xxx\\\" caused \\\"stat /C/Users/xxx/workspace/go/src/github.com/xxx: input/output error\\\"\""
Encountered errors while bringing up the project.
@greed2411

This comment has been minimized.

Copy link

greed2411 commented Nov 24, 2017

Hi.
Im having similar problem. Newb here.
I tried to install this image.

It did fit well. But when i try to run,

 $ sudo docker run -ti --rm -v ~/Downloads:/Downloads bwits/pdf2htmlex --zoom 1.3 1.pdf

it throws,

docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"--zoom\": executable file not found in $PATH".

Already tried sudo didn't seem to work.

Information regarding docker install

 $ sudo docker version
Client:
 Version:      17.09.0-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:42:18 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.09.0-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:40:56 2017
 OS/Arch:      linux/amd64
 Experimental: false

docker info

 $ sudo docker info
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 2
Server Version: 17.09.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.8.0-59-generic
Operating System: Ubuntu 16.10
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.691GiB
Name: greyhound
ID: ZNTB:2MIN:NYGC:GQKD:DWWM:K7CX:ELML:KIX7:WYFT:VJQX:4POJ:POPL
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

@bhargav3

This comment has been minimized.

Copy link

bhargav3 commented Nov 30, 2017

A reboot worked for me :-/

@scythargon

This comment has been minimized.

Copy link

scythargon commented Dec 5, 2017

Same here, reboot didn't help:(
Host - ubuntu.
Everything works fine, but not when I installed a gitlab-runner on it and trying to execute docker-compose in it.
Have anybody figured it out already?

@Chematronix

This comment has been minimized.

Copy link

Chematronix commented Dec 6, 2017

Fixed by editing mount folders in Kitematic. They first appeared repeated (Docker folder: /var/www/html/something, Local folder: /var/www/html/something). After editing, they appear garbled (Local folder: \d\srvT:est\something instead of \d\srv\test\something), but they work. In the error message, the unit drive is in caps (stat /D/srv/test/something: input/output error).

This on my PC running Windows 10 with Hyper-V. I don't intend to install Kitematic (+X) in my server tho, so this is more of a temporal workaround...

@AdamZaczek

This comment has been minimized.

Copy link

AdamZaczek commented Dec 23, 2017

I also had this error on MacOS, resetting the docker fixed it somehow.

@obfusticatedcode

This comment has been minimized.

Copy link

obfusticatedcode commented Jan 4, 2018

If you're using MacOS, you should make your host's docker-entrypoint.sh executable too, not just on your Dockerfile. Got this from a tip, https://github.com/composer/docker/issues/7

@dan-lootcrate

This comment has been minimized.

Copy link

dan-lootcrate commented Jan 5, 2018

@obfusticatedcode this fixed my problem! I was tearing my head out wondering why this project worked great on my Windows workstation but was crapping out on my Macbook Pro. Thanks!

@qfsf0220

This comment has been minimized.

Copy link

qfsf0220 commented Feb 5, 2018

In my case , yum install libseccomp libseccomp-devel.

@weholt

This comment has been minimized.

Copy link

weholt commented Feb 15, 2018

I was using alpine-based images and changed /bin/bash to /bin/sh and it worked ok :-)

@pablomalo

This comment has been minimized.

Copy link

pablomalo commented Feb 19, 2018

Want to thank @obfusticatedcode ! Problem solved. In my case, the project worked on Windows but failed upon running docker-compose up on Debian.

@iabtyagi

This comment has been minimized.

Copy link

iabtyagi commented Jun 28, 2018

Faced and solved the same issue. For me, it was due to the service level volumes declaration in the docker-compose.yml file.

services:
  web:
    volumes:
      - ./app/:/app 

This was overriding anything I copied to /app mount point in the Dockerfile.
Commenting out the volumes declaration worked.

@subhash-shah

This comment has been minimized.

Copy link

subhash-shah commented Jun 28, 2018

I could make it work on Windows 10 after running the command prompt as an administrator.

@danielcgithub

This comment has been minimized.

Copy link

danielcgithub commented Aug 26, 2018

issue for me was that I recently changed windows password, Going into Docker settings -> shared drives, un-selecting my drive, apply, and then re-selecting (apply) fixed it.

@WinstonN

This comment has been minimized.

Copy link

WinstonN commented Aug 28, 2018

@sajadghawami I wanted to thank you, personally, for saving me from this hell. Your comment was invaluable!! Thank you <3

@mparker11

This comment has been minimized.

Copy link

mparker11 commented Sep 28, 2018

On windows 10 and just encountered this bug. Going into Docker settings -> shared drives and then unselecting my drive, apply, and then re-selecting (apply) seems to have fixed it. Thanks @artem-gavrylenko

This was perfect. Why do things like this happen?? Does anyone know?

@elminson

This comment has been minimized.

Copy link

elminson commented Nov 7, 2018

Yo can look for /docker-entrypoint-initdb.d in the volumes section if the sql file don't exist will return this error.

mysql:
     image: percona:5.6
     ports:
       - "3306:3306"
     volumes:
       - ./sql/bk.sql:/docker-entrypoint-initdb.d/bk.sql # bk.sql don't exist, comment the line or put the file there 
       - ./docker/mysql:/var/lib/mysql
@kilitary

This comment has been minimized.

Copy link

kilitary commented Nov 11, 2018

Same error

PS D:\projects\bp> docker info
Containers: 5
 Running: 2
 Paused: 0
 Stopped: 3
Images: 3
Server Version: 18.09.0
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.14.79-boot2docker
Operating System: Boot2Docker 18.09.0 (TCL 8.2.1)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 989.4MiB
Name: vm
ID: JWYK:OSFS:XCAW:W2MF:FZZT:BBTD:EKCN:WH55:4YGD:V634:O37T:7JJL
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
PS D:\projects\bp> docker version                   
Client:                                             
 Version:           18.06.1-ce                      
 API version:       1.38                            
 Go version:        go1.10.3                        
 Git commit:        e68fc7a                         
 Built:             Tue Aug 21 17:21:34 2018        
 OS/Arch:           windows/amd64                   
 Experimental:      false                           
                                                    
Server: Docker Engine - Community                   
 Engine:                                            
  Version:          18.09.0                         
  API version:      1.39 (minimum version 1.12)     
  Go version:       go1.10.4                        
  Git commit:       4d60db4                         
  Built:            Wed Nov  7 00:52:55 2018        
  OS/Arch:          linux/amd64                     
  Experimental:     false                           

docker-compose.tml:


version: '3.4'
services:
    web:
        image: nginx:alpine
        container_name: ${NGINX_HOST}
        ports:
        - "80:80"
        - "443:443"
        env_file:
        - ".env"
        environment:
        - NGINX_HOST=${NGINX_HOST}
        #command: /bin/sh -c "envsubst < /etc/nginx/conf.d/default.template > /etc/nginx/conf.d/default.conf" && nginx -g 'daemon off;'
        restart: always
        depends_on:
        - php
        - mysqldb
        logging:
          driver: json-file
          options:
            max-size: "200k"
            max-file: "10"
        volumes:
        - ./etc/nginx/default.conf:/etc/nginx/conf.d/default.conf
        - ./etc/nginx/default.template:/etc/nginx/conf.d/default.template
        - ./etc/ssl:/etc/ssl
        - .:/var/www/html
    php:
        image: nanoninja/php-fpm:${PHP_VERSION}
        restart: always
        volumes:
        - ./etc/php/php.ini:/usr/local/etc/php/conf.d/php.ini
        - .:/var/www/html
        links:
        - mysqldb
    mysqldb:
        image: mysql:${MYSQL_VERSION}
        container_name: ${MYSQL_HOST}
        restart: always
        env_file:
        - ".env"
        environment:
        - MYSQL_DATABASE=${MYSQL_DATABASE}
        - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
        - MYSQL_USER=${MYSQL_USER}
        - MYSQL_PASSWORD=${MYSQL_PASSWORD}
        privileged: true
        ports:
        - "8989:3306"
        volumes:
        - ../db:/var/lib/mysql
        #- ./etc/mysql/my.cnf:/etc/mysql/my.cnf


PS D:\projects\bp> docker-compose up web
Removing bp.int
mysql is up-to-date
bp_php_1 is up-to-date
Starting 0ef479e51d62_bp.int ... error

ERROR: for 0ef479e51d62_bp.int  Cannot start service web: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/d/projects/bp/etc/nginx/default.conf\\\" to rootfs \\\"/mnt/sda1/var/lib/docker/overlay2/a5cad006b2a324c1026e2d98a466e9ed454971961d166bfb4f7b5f5ec82605b3/merged\\\" at \\\"/mnt/sda1/var/lib/docker/overlay2/a5cad006b2a324c1026e2d98a466e9ed454971961d166bfb4f7b5f5ec82605b3/merged/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for web  Cannot start service web: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/d/projects/bp/etc/nginx/default.conf\\\" to rootfs \\\"/mnt/sda1/var/lib/docker/overlay2/a5cad006b2a324c1026e2d98a466e9ed454971961d166bfb4f7b5f5ec82605b3/merged\\\" at \\\"/mnt/sda1/var/lib/docker/overlay2/a5cad006b2a324c1026e2d98a466e9ed454971961d166bfb4f7b5f5ec82605b3/merged/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
@jmrieger

This comment has been minimized.

Copy link

jmrieger commented Nov 20, 2018

A teammate just ran into this issue. @sajadghawami's solution worked for us.

One note about the situation that may have caused this - she changed her Windows password the day before. While I don't have the personal resources to validate this behavior, I think it would be easy to test that.

@fippy

This comment has been minimized.

Copy link

fippy commented Dec 15, 2018

I've been pulling my hair out for some time now as I cannot get reaction to install following the instructions at https://docs.reactioncommerce.com/docs/next/installation-reaction-platform.

I'm running Windows 7 64-bit Pro with node.js 8.12.0 and rather than use the latest installer which is only compatible with Windows 10, I have sucessfully installed Many steps complete successfully Docker Toolbox which contains Docker Engine as well as Oracle VM. All good so far.

I've configured GitHub with SSH and sucessfully cloned the reaction project using git.

When I run the make command, many steps completed successfully, but it keeps failing at step 40/41 with the below error. (Note: To create the two networks auth.reaction.localhost and api.reaction.localhost I had to turn off Windows Firewall and run the docker network create commands manually.)

Step 41/41 : CMD ["yarn", "start"]
 ---> Running in 237f6ba37bc1
Removing intermediate container 237f6ba37bc1
 ---> a3936c5854f2

Successfully built a3936c5854f2
Successfully tagged reactionnextstarterkit_web:latest
Running post-build hook script for reaction-next-starterkit.
reaction-next-starterkit post-build script invoked.
Recreating reactionnextstarterkit_web_1 ... error

ERROR: for reactionnextstarterkit_web_1  Cannot start service web: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/usr/local/src/reaction-app/bin/start\": stat /usr/local/src/reaction-app/bin/start: no such file or directory": unknown

ERROR: for web  Cannot start service web: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/usr/local/src/reaction-app/bin/start\": stat /usr/local/src/reaction-app/bin/start: no such file or directory": unknown
ERROR: Encountered errors while bringing up the project.
make: *** [start-reaction-next-starterkit] Error 1

Any help or pointers would be HUGELY appreciated!

@fippy

This comment has been minimized.

Copy link

fippy commented Dec 15, 2018

If anyone is interested I managed to get install to complete on Windows by copying the reaction-platform folder under the User directory... (I think it was some kind of permissions issue perhaps?)

Anyway I still haven't managed to get it to run by following the developer instructions outlined and simply running the 'make' command in the reaction-platform directory.

So far instructions for windows developers have been VERY POOR - a huge shame IMO

@jasie

This comment has been minimized.

Copy link

jasie commented Dec 17, 2018

issue for me was that I recently changed windows password, Going into Docker settings -> shared drives, un-selecting my drive, apply, and then re-selecting (apply) fixed it.

thank you SO MUCH, @danielcgithub. saved my day.

@haarts

This comment has been minimized.

Copy link

haarts commented Dec 17, 2018

For what it is worth: sudo docker container prune fixed the issue for me.

@n0minal

This comment has been minimized.

Copy link

n0minal commented Jan 2, 2019

click on icon tray Docker > Settings... > Shared Drivers and select checkbox Shared: C and D
Maybe it`s help you!

Tu é pica mesmo

@ashireman

This comment has been minimized.

Copy link

ashireman commented Jan 4, 2019

click on icon tray Docker > Settings... > Shared Drivers and select checkbox Shared: C and D
Maybe it`s help you!

A teammate just ran into this issue. @sajadghawami's solution worked for us.

One note about the situation that may have caused this - she changed her Windows password the day before. While I don't have the personal resources to validate this behavior, I think it would be easy to test that.

Just to add in to the other comments here by several people, this happened to me recently and I can confirm. I had recently changed the password, computer was restarted and docker-compose would not bring up the containers. Unchecking and rechecking the Shared Drive, followed by entering the updated password got everything up and running.

@marlonoso

This comment has been minimized.

Copy link

marlonoso commented Feb 7, 2019

It fails when setting entrypoint as per documentation

version: '3.2'
services:
  my_service:
    image: my_image
    volumes:
      - /home/app/config:/root
    entrypoint:
      - ls /root

It works when changing entrypoint to

    entrypoint:
      ls /root

without hiphen

@firezdog

This comment has been minimized.

Copy link

firezdog commented Feb 13, 2019

I had this happen when trying to run a docker through docker toolbox in windows on WSL. For what it's worth to anyone here, my problem was solved by making sure that i was accessing things through the windows rather than the linux file-system:

docker run -it --rm --name lispy -v "$PWD":/Lis_Py python:3 python Lis_Py/lis.py || docker start -ia lispy

# on WSL with docker running in windows, $PWD will not work and must be set to the same as $PWD from docker quick-start,
# viz. docker run -it --rm --name lispy -v /c/Users/firez/Documents/Development/lis.py:/Lis_Py python:3 python Lis_Py/lis.py || docker start -ia lispy

@yujunhui

This comment has been minimized.

Copy link

yujunhui commented Mar 15, 2019

what happen

I face the "OCI runtime create failed" error too.
here is my command docker-compose up -d

how I solved

I login server by ssh -A, and then, error occur.
I logout and login by ssh without params, everything right.

log

ERROR: for my_logstash  Cannot start service logstash: OCI runtime create failed: container_linux.go:344: starting contain
er process caused "process_linux.go:297: getting the final child's pid from pipe caused \"EOF\"": unknown

ERROR: for logstash  Cannot start service logstash: OCI runtime create failed: container_linux.go:344: starting container proc
ess caused "process_linux.go:297: getting the final child's pid from pipe caused \"EOF\"": unknown
ERROR: Encountered errors while bringing up the project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.