blocks|key|47087|text|我发现了同样的问题。我做了以下工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|47088|docker+run+-ti+devops+-v+/tmp:/tmp+/bin/bash|code-block|syntax|javascript|47089|当我将其更改为|47090|docker+run+-ti+-v+/tmp:/tmp+devops+/bin/bash|47091|它工作得很好。|47092|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I found the same problem. I did the following:

<pre><code>docker run -ti devops -v /tmp:/tmp /bin/bash
</code></pre>

When I change it to

<pre><code>docker run -ti -v /tmp:/tmp devops /bin/bash
</code></pre>

it works fine.

blocks|key|4553701|text|出现这样的错误有几种可能的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4553702|在我的例子中，这是由于可执行文件(来自Ghost+blog+Dockerfile的docker-entrypoint.sh)在我下载之后缺少可执行文件模式。|offset|length|style|CODE|4553703|解决方案：chmod+%2Bx+docker-entrypoint.sh|4553704|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker-library/ghost/blob/1249536b0b8135179230174fa8a89e68e92f8c25/1/debian/Dockerfile^0|0|15|K|J|L|0|0|5|T|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@$D|V|E|W|1|X]]|A|$]]|$1|H|3|I|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

There are several possible reasons for an error like this.

In my case, it was due to the executable file (<code>docker-entrypoint.sh</code> from the <a href="https://github.com/docker-library/ghost/blob/1249536b0b8135179230174fa8a89e68e92f8c25/1/debian/Dockerfile" rel="noreferrer">Ghost blog Dockerfile</a>) lacking the executable file mode after I'd downloaded it. 

Solution: <code>chmod +x docker-entrypoint.sh</code>

blocks|key|4553718|text|要使其正常工作，请将软引用添加到/usr/bin：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4553719|ln+-s+$(哪个节点)+/usr/bin/node|4553720|ln+-s+$(哪个npm)+/usr/bin/npm|4553721|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

to make it work add soft reference to /usr/bin:

<h1>
ln -s $(which node) /usr/bin/node
</h1>

<h1>
ln -s $(which npm) /usr/bin/npm
</h1>

blocks|key|4553773|text|由于某种原因，除非我添加了"bash“澄清符，否则我会得到这个错误。甚至在我的入口点文件的顶部添加"#!/bin/bash“也没有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4553774|ENTRYPOINT+[+"bash",+"entrypoint.sh"+]|code-block|syntax|javascript|4553775|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For some reason, I get that error unless I add the "bash" clarifier. Even adding "#!/bin/bash" to the top of my entrypoint file didn't help. 

<pre><code>ENTRYPOINT [ "bash", "entrypoint.sh" ]
</code></pre>

blocks|key|4553792|text|Docker容器可以在没有外壳的情况下构建(例如https://github.com/fluent/fluent-bit-docker-image/issues/19)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4553793|在这种情况下，您可以复制一个静态编译的shell并执行它，例如|4553794|docker+create+--name+temp-busybox+busybox:1.31.0
docker+cp+temp-busybox:/bin/busybox+busybox
docker+cp+busybox+mycontainerid:/busybox
docker+exec+-it+mycontainerid+/bin/busybox+sh|code-block|syntax|javascript|4553795|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/fluent/fluent-bit-docker-image/issues/19^0|O|1N|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

A Docker container might be built without a shell (e.g. <a href="https://github.com/fluent/fluent-bit-docker-image/issues/19" rel="noreferrer">https://github.com/fluent/fluent-bit-docker-image/issues/19</a>).

In this case, you can copy-in a statically compiled shell and execute it, e.g.

<pre><code>docker create --name temp-busybox busybox:1.31.0
docker cp temp-busybox:/bin/busybox busybox
docker cp busybox mycontainerid:/busybox
docker exec -it mycontainerid /bin/busybox sh
</code></pre>

blocks|key|47287|text|问题是glibc，它不是apline基本图像的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|47288|添加后，它为我工作:)|47289|下面是获取glibc的步骤|47290|apk+--no-cache+add+ca-certificates+wget
wget+-q+-O+/etc/apk/keys/sgerrand.rsa.pub+https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub
wget+https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.28-r0/glibc-2.28-r0.apk
apk+add+glibc-2.28-r0.apk|code-block|syntax|javascript|47291|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

problem is glibc, which is not part of apline base iamge.
After adding it worked for me :)
Here are the steps to get the glibc
<pre><code>apk --no-cache add ca-certificates wget
wget -q -O /etc/apk/keys/sgerrand.rsa.pub https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub
wget https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.28-r0/glibc-2.28-r0.apk
apk add glibc-2.28-r0.apk
</code></pre>

blocks|key|4553835|text|我在使用docker-compose时遇到了这个问题。这里或this+related+question上的解决方案都没有解决我的问题。最终，对我起作用的是用docker+prune+-a清除所有缓存的docker工件并重新启动docker。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4553836|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/q/48001082/2121777^0|4|E|26|F|U|L|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

I ran into this issue using <code>docker-compose</code>. None of the solutions here or on <a href="https://stackoverflow.com/q/48001082/2121777">this related question</a> resolved my issue. Ultimately what worked for me was clearing all cached docker artifacts with <code>docker prune -a</code> and restarting docker.

I have a docker image which installs <code>grunt</code>, but when I try to run it, I get an error: 

<pre><code>Error response from daemon: Cannot start container foo_1: \
 exec: "grunt serve": executable file not found in $PATH
</code></pre>

If I run bash in interactive mode, <code>grunt</code> is available.

What am I doing wrong?

Here is my Dockerfile:

<pre><code># https://registry.hub.docker.com/u/dockerfile/nodejs/ (builds on ubuntu:14.04)
FROM dockerfile/nodejs

MAINTAINER My Name, me@email.com

ENV HOME /home/web
WORKDIR /home/web/site

RUN useradd web -d /home/web -s /bin/bash -m

RUN npm install -g grunt-cli
RUN npm install -g bower

RUN chown -R web:web /home/web
USER web

RUN git clone https://github.com/repo/site /home/web/site

RUN npm install
RUN bower install --config.interactive=false --allow-root

ENV NODE_ENV development

# Port 9000 for server
# Port 35729 for livereload
EXPOSE 9000 35729
CMD ["grunt"]
</code></pre>

docker: executable file not found in $PATH

容器

Docker

我有一个安装grunt的docker镜像，但当我尝试运行它时，我得到一个错误：Error response from daemon: Cannot start container foo_1: \    exec: "grunt serve": executable file not found in $PATH如果我...

问docker:在$PATH中找不到可执行文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker:在$PATH中找不到可执行文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker:在$PATH中找不到可执行文件
EN