
Loading…
`no such file or directory` error after upgrading to 0.7.3 #3451
The same happens for me (also after an apt-get update).
I'm seeing the same, but only on my devicemapper box, not on AUFS. The AUFS machine works flawlessly, but the exact same Dockerfile gives me no such file or directory. For me, it's not happening on the apt-get update itself, but after the entire RUN line (which also includes an apt-get install).
Here's a minimal Dockerfile that replicates this on devicemapper on my machine (simplified from what I was testing with when I ran into this originally):
FROM debian:sid
RUN apt-get update
Even more easily tested with echo -e 'FROM debian:sid\nRUN apt-get update' | docker build -rm -.
I also tested all these RUN commands instead of apt-get update, but they all build successfully just fine:
RUN echo hiRUN touch /helloRUN touch /var/run/something-
RUN touch /var/lib/something(just testing a few paths that might be suspect, especially since /var/run is a symlink to /run)
Not sure what would be most useful to test next, but of course always happy to do so.
Closing as duplicate
Hi, sorry if this isn't the right place to report this or if it's already been reported, but after I upgraded from Docker 0.7.2 to 0.7.3, a Dockerfile I'm working with fails to run
apt-get updatewith the following error message.I'm running this in Arch Linux, and the Docker version for this was:
After downgrading back to:
this error doesn't occur.
Let me know if I can provide more info. Thanks!