On Wednesday, 30 January 2019 11:45:33 CET Arnaud Rebillout wrote:
> Could it be a matter of `systemctl restart docker`, or something like
> that?
spot on !
docker is working fine after a restart.
Thanks for the hint.
Dod
> On Wednesday, 30 January 2019 7:59:24 PM AEDT Dominique Dumont wrote:
>> But docker fails to start with:
>> $ docker run -ti alpine sh
>> docker: Error response from daemon: failed to start shim: exec:
>> "docker-containerd-shim": executable file not found in $PATH: unknown.
I can run `docker
On Wednesday, 30 January 2019 7:59:24 PM AEDT Dominique Dumont wrote:
> But docker fails to start with:
> $ docker run -ti alpine sh
> docker: Error response from daemon: failed to start shim: exec:
> "docker-containerd-shim": executable file not found in $PATH: unknown.
Ahh, what a mess... I'll h
On Mon, 28 Jan 2019 13:53:08 +1100 Dmitry Smirnov wrote:
> On Monday, 28 January 2019 2:26:00 AM AEDT Holger Schröder wrote:
> > sorry, is not solved. next problem.
> >
> > docker run -it -u0 --rm alpine:latest
> > docker: Error response from daemon: failed to start shim: exec:
> > "containerd-sh
On Monday, 28 January 2019 2:26:00 AM AEDT Holger Schröder wrote:
> sorry, is not solved. next problem.
>
> docker run -it -u0 --rm alpine:latest
> docker: Error response from daemon: failed to start shim: exec:
> "containerd-shim": executable file not found in $PATH: unknown.
Apologies for troub
sorry, is not solved. next problem.
docker run -it -u0 --rm alpine:latest
docker: Error response from daemon: failed to start shim: exec:
"containerd-shim": executable file not found in $PATH: unknown.
On Sunday, 27 January 2019 7:21:26 PM AEDT Holger Schröder wrote:
> The last docker.io update (18.09.1+dfsg1-2) docker no longer starts. The
> output of 'systemctl start docker.service' see attached logfile
Thanks for letting me know but next time please report a bug [1] so others
will be aware o
7 matches
Mail list logo
