These are chat archives for hypriot/talk

7th
Feb 2016
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 16:48
Hi there, I am running into troubles when upgrading to Docker 1.10 :-(
I used the command sudo dpkg -i docker-hypriot_1.10.0-1_armhf.deb after downloading the file
I got some errors when installing it
$ sudo dpkg -i docker-hypriot_1.10.0-1_armhf.deb
(Reading database ... 53240 files and directories currently installed.)
Preparing to unpack docker-hypriot_1.10.0-1_armhf.deb ...
Unpacking docker-hypriot (1.10.0-1) over (1.10.0-1) ...
Setting up docker-hypriot (1.10.0-1) ...
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker-hypriot (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (215-17+deb8u2) ...
Errors were encountered while processing:
   docker-hypriot
docker -v works perfectly
but trying "docker run hello-world" just hangs.
Any idea ?
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 17:02
Additional info:
```
HypriotOS: pi@my-pi3 in ~
$ systemctl status docker.service
ā— docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Active: failed (Result: exit-code) since Sun 2016-02-07 17:59:31 CET; 1min 46s ago
Docs: https://docs.docker.com
Main PID: 1020 (code=exited, status=2)
HypriotOS: pi@my-pi3 in ~
$ sudo journalctl -xn
-- Logs begin at Sun 2016-02-07 17:22:03 CET, end at Sun 2016-02-07 18:02:00 CET. --
Feb 07 17:58:02 my-pi3 docker[1020]: time="2016-02-07T17:58:02.215156543+01:00" level=debug msg="layer f3e9ecfc7065b2b6ebebadd1a8b48bc32a6c4bda265fcaf4c8b38b46ea756fbe took 0.00 sec
Feb 07 17:58:02 my-pi3 docker[1020]: time="2016-02-07T17:58:02.215550706+01:00" level=debug msg="layer faa3e8795c2e0cf307e8c94b9d02c143e32311092637dfa4379dd2a2308d0bd8 took 0.00 sec
Feb 07 17:59:31 my-pi3 systemd[1]: docker.service start operation timed out. Terminating.
Feb 07 17:59:31 my-pi3 systemd[1]: docker.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Feb 07 17:59:31 my-pi3 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Feb 07 17:59:31 my-pi3 systemd[1]: Unit docker.service entered failed state.
Feb 07 17:59:31 my-pi3 systemd[1]: Reloading.
Feb 07 17:59:32 my-pi3 sudo[885]: pam_unix(sudo:session): session closed for user root
Feb 07 18:02:00 my-pi3 sudo[1058]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xn
Feb 07 18:02:00 my-pi3 sudo[1058]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
sorry for the mixup in the quotes
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 17:40
Additional note: starting from a newly flashed SD works
I wonder if the already loaded images were'nt in the way.
"on the road again..." until the next roadblock ;-)
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 18:51
I had to update docker-compose by hand with sudo apt-get install docker-compose
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 18:56
I found this article about updating images to the new format: https://blog.docker.com/2016/01/docker-1-10-rc/
it seems that there is a utility to convert the images. but it doesn't exist for ARM
Martin Honermeyer
@djmaze
Feb 07 2016 19:00
@jmMeessen If you can afford 10 minutes of downtime, just restart the Docker daemon and wait for the migration to finish.
Stefan Scherer
@StefanScherer
Feb 07 2016 19:00
@jmMeessen yes it seems you have a lot of images on your RPi. That's the reason for "hanging" updates. calculating the new checksums/ids takes some time. I haven't tried to build the conversion utility for ARM.
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 19:49
@StefanScherer @djmaze
Aaaah, I understand. As I am testing, I am probably to impatient.
Did I understand correctly the protocol ? I upgrade to Docker v1.10 (and get the error message). I stop the deamon and just restart it and wait (and not cancel it after a minute)
Stefan Scherer
@StefanScherer
Feb 07 2016 20:05
You can check /var/log/docker.log or syslog to see some progress.
Jean-Marc MEESSEN
@jmMeessen
Feb 07 2016 20:21
Yeah.
Exact sequence that worked for me is sudo service docker stop and then sudo docker daemon. I had indeed many layers/images. Launching sudo service docker start failed with a timeout.