Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

exec: "/bin/echo": stat /bin/echo: no such file or directory #15

Closed
Jamlee opened this issue Mar 27, 2015 · 11 comments
Closed

exec: "/bin/echo": stat /bin/echo: no such file or directory #15

Jamlee opened this issue Mar 27, 2015 · 11 comments

Comments

@Jamlee
Copy link

Jamlee commented Mar 27, 2015

when I stop all container and restart all,I occur that "exec: "/bin/echo": stat /bin/echo: no such file or directory"

@bedeoverend
Copy link

Yup I get the same issue unfortunately

@kasperisager
Copy link
Owner

I'm investigating.

@kasperisager
Copy link
Owner

Feck, a998e14 didn't survive a restart.

@kasperisager
Copy link
Owner

The issue is related to docker/compose#919.

@bedeoverend
Copy link

Damn. So no fix on the horizon?

@kasperisager
Copy link
Owner

I'm afraid not. A workaround is to do docker-compose rm shipyard prior to every up or simply commenting out the Shipyard container in docker-compose.yml.

@kasperisager
Copy link
Owner

Looks like a fix is scheduled for Compose 1.3.0: docker/compose#1349

@kasperisager
Copy link
Owner

The above mentioned fix has been merged so hopefully this issue will resolve itself by the time Compose 1.3.0 hits the deck.

@dydx
Copy link

dydx commented Jun 5, 2015

I'm experiencing this tonight. I'm trying out just dropping the shipyard stuff from docker-compose.yml as a quick workaround 🎱

@math3vz
Copy link

math3vz commented Sep 5, 2015

For me, updating to docker-compose 1.4.0 solved the problem. Anyone else?

@kasperisager
Copy link
Owner

Compose 1.4 has been out for a while so I'll close this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants