Closed tuliomonteazul closed 8 years ago
This error happens sometimes with me too. :( Would be nice if I could easy simulate this to fix that.
@saitodisse , I guess using the same Dockerfile the problem should be repeated?
This happens randomly to me too. I think it's usually first time we do azk start on a new machine, but could be wrong about that.
Yes @slobo, you are right. Every time when pulling new images this happens.
To simulate that behaviour I did this, with a Dockerfile using nodesource/node:0.12
:
azk stop; /
sudo service docker restart; /
adocker rmi -f nodesource/node:0.12; /
adocker rmi -f $(adocker images -q -f dangling=true | tr '\r\n' ' '); /
azk start -Rvv; /
sudo service docker restart;
I will try to fix this now
Running on Mac OS X 10.9.5 Azk version 0.15.0
After running
azk start -R -vv
, a lot ofundefined
values were printed incrementally. Probably has something to do with the image download progress. Running the same command again didn't reproduce the problem. Deleting the image withadocker rmi -f
and running the same command, reproduced the problem.Here is an image:
My Azkfile has:
image: {"dockerfile": "./docker/Dockerfile"},
My Dockerfile is: