coppit Posted June 5, 2015 Share Posted June 5, 2015 unRAID OS Version: 6.0-rc4 Description: When trying to pull images or do anything with the server, docker fails with a certificate error. How to reproduce: docker pull coppit/duckdns Expected results: Image is pulled Actual results: $ docker pull coppit/duckdns Pulling repository coppit/duckdns FATA[0000] Get https://index.docker.io/v1/repositories/coppit/duckdns/images: x509: failed to load system roots and no roots provided Other information: $ docker login Username: coppit Password: Email: [email protected] FATA[0006] Error response from daemon: Server Error: Post https://index.docker.io/v1/users/: x509: failed to load system roots and no roots provided $ ls /var/log/packages/ | grep cert ca-certificates-20130906-noarch-1 (root @ storage) : /mnt/vms/templates-user $ date Thu Jun 4 23:01:40 EDT 2015 That is the correct date. In this thread: http://lime-technology.com/forum/index.php?topic=40363.0 I describe being able to pull an image briefly, after restarting docker. But now the problem is back, and restarting doesn't help. I have moved docker.img to docker.img.bak and recreated docker.img, but the issue still repros. Perhaps this is relevant? https://github.com/docker/docker/issues/5157#issuecomment-95731375 Also, I accidentally filled up my docker.img a while back. I cleaned some old images and such and it worked better. That's why I started with a new docker.img, to rule that out. BTW, the wget above didn't work at first. I had to run "trolley install -f ca-certificates" for it to succeed without complaining about the github cert. But that didn't help with docker. Can someone running 6.0-rc4 please confirm that they can pull some docker image that they've never pulled before? That would help determine if it's "just me". Link to comment
trurl Posted June 5, 2015 Share Posted June 5, 2015 trolley is a third party addon and its author hasn't been seen around here in quite some time. Maybe not relevant, but since it doesn't have any visible means of support you might want to remove it. Link to comment
coppit Posted June 5, 2015 Author Share Posted June 5, 2015 That comment got me thinking... I haven't looked in /boot/extras lately. With everything moving to plugins and docker lately, the only reason I was using trolley was to install vim. After moving those packages out of /boot/extra, things are working again. Woot! Link to comment
RobJ Posted June 5, 2015 Share Posted June 5, 2015 Trolley was all 32 bit, and that would cause strange problems! In the Upgrading to UnRAID v6 guide, there's a small section on Obsolete Plugins, which mentions Control Panel, Trolley, Boiler, and every other plugin that does not mention being updated for v6. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.