moby: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/registry\": executable file not found in $PATH": unknown.

Run docker run -d --name test test, I got the following error. docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused “exec: "/registry": executable file not found in $PATH”: unknown.

docker info:

Containers: 7
 Running: 0
 Paused: 0
 Stopped: 7
Images: 65
Server Version: 18.03.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: false
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: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-514.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 62.25GiB
Name: CTU1000117562
ID: GFZZ:GSOG:WB7M:CGRO:BTOL:TAWE:HTQA:RVTG:3SMX:OB56:WQ6V:VJ63
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 http://9f8a9340.m.daocloud.io/
Live Restore Enabled: false

docker version

Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   9ee9f40
 Built:        Thu Apr 26 07:20:16 2018
 OS/Arch:      linux/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   9ee9f40
  Built:        Thu Apr 26 07:23:58 2018
  OS/Arch:      linux/amd64
  Experimental: false

My Dockerfile

FROM golang:1.10-alpine

ENV DISTRIBUTION_DIR /go/src/github.com/docker/distribution
ENV DOCKER_BUILDTAGS include_oss include_gcs include_obs

ARG GOOS=linux
ARG GOARCH=amd64

RUN set -ex \
    && apk add --no-cache make git

WORKDIR $DISTRIBUTION_DIR
COPY . $DISTRIBUTION_DIR
COPY cmd/registry/config-dev.yml /etc/docker/registry/config.yml

RUN make PREFIX=/go clean binaries

VOLUME ["/var/lib/registry"]
EXPOSE 5000
ENTRYPOINT ["registry"]
CMD ["serve", "/etc/docker/registry/config.yml"]

Really need some help and insights! Thx

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 3
Comments: 28 (7 by maintainers)

Most upvoted comments

“chmod +x”. Closing because this is not a Docker issue. Thanks!

+106

cpuguy83 on Aug 24, 2018

I closed the terminal and open again - it helped 😄

+11

dudziakm on Aug 2, 2019

This is happening to a lot of people and I’m experiencing this on a very stubborn install situation. It seems the up-to-date install instruction no longer work for Docker CE on a Ubuntu 18.04 install. This issue happens on ALL attempts to run ANY container. That leads me to believe this is actually related to Docker itself, not a permissions with any file within the containers. I have been without luck for several days, to solve this problem. Maybe it’s time i leave Ubuntu because this OS is the only one I keep running into issues with regarding Docker.

maietta on Dec 24, 2018

@cpuguy83 could you clarify or reopen the issue?

luckydonald on Jan 2, 2020

@charan432 what image are you trying to run, and what’s the command you’re trying to run in it? If the command is a shell-script, make sure that it’s executable (see above), but also that it has Linux line-endings (\n), not windows (\r\n). Linux reports “executable file not found” if a shell-script has Windows line-endings (which is very confusing, but unfortunately how Linux reports it)

thaJeztah on Jan 24, 2019

Problem still exists after installing an ubuntu/trusty64 on virtualbox and following the official docker install description.

sz332 on Mar 23, 2019

Your arguments are in the wrong order. “-it” needs to go before the image name.

cpuguy83 on Mar 5, 2019

@thaJeztah I seem to have the same problem, but only when running docker in some kind of a virtual environment:

xubuntu bionic (“metal” laptop): Succes xubuntu bionic (virtualbox, host xubuntu bionic, guest xubuntu bionic) : Failure xubuntu bionic (virtualbox, host windows 7, guest xubuntu bionic) : Failure xubuntu bionic (xen hypervisor, dom0 debian jessie, guest xubuntu bionic, paravirtualized) : Failure xubuntu bionic (xen hypervisor, dom0 debian jessie, guest xubuntu bionic, hardware virtualization) : Failure

In all cases, I used a barebone ubuntu image and tried running the command /bin/ls, ie. "docker run ubuntu /bin/ls"

“failure” means the error reported by @charan432

I have used the docker-ce 18.09.1~3-0, docker-ce-cli 18.09.1~3-0 and containerd.io 1.2.2-1 debian packages for bionic ubuntu provided from `https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/amd64/

`Please let me know if I can provide anything else (logfiles, additional tests, whatever) to help solve this bug: It really is a showstopper for my current project 😦

UPDATE: turns out the virtual environment thing was a red herring. From what I can see now, any image imported via docker import fails with the above error on an updated bionic system. I’ll open a new issue…

UPDATE UPDATE: and then I found docker load. Nevermind this post…

vdf-git on Jan 29, 2019