I should probably be doing my work in a VM or container, but I'm working on a docker container that uses the "webdizz/docker-baseimage-java8" base.

 

When I run "docker build", I get this error:

 

Sending build context to Docker daemon 198.1 kB
Sending build context to Docker daemon
Step 0 : FROM webdizz/docker-baseimage-java8
Pulling repository webdizz/docker-baseimage-java8
INFO[0000] Get https://index.docker.io/v1/repositories/webdizz/docker-baseimage-java8/images: x509: failed to load system roots and no roots provided

 

I ran

update-ca-certificates

and it didn't help. I see 165 certificates in /etc/ssl/certs.

 

Has anyone else run into this?

nope, but i have a fix.

 

why not just use phusion, and then run everything that makes that a java8 baseimage ?

 

 

 

FROM phusion/baseimage:0.9.16

MAINTAINER Izzet Mustafaiev "[email protected]"

# Set correct environment variables.
ENV	HOME /root
ENV	LANG en_US.UTF-8
ENV	LC_ALL en_US.UTF-8
ENV	DEBIAN_FRONTEND	noninteractive

# set sane locale
RUN	locale-gen en_US.UTF-8

RUN apt-get -y update \
&& apt-get -y install software-properties-common python-software-properties \
&& add-apt-repository ppa:webupd8team/java \
&& apt-get clean \
&& apt-get -y update \
    && echo oracle-java8-installer shared/accepted-oracle-license-v1-1 select true | /usr/bin/debconf-set-selections \
    && apt-get -y install oracle-java8-installer \
    && apt-get clean \
    && update-alternatives --display java \
    && rm -rf /build \
    && rm -rf /tmp/* /var/tmp/* \
    && rm -rf /var/lib/apt/lists/* \
    && apt-get remove -y x11-common software-properties-common python-software-properties python3-software-properties

ENV JAVA_HOME /usr/lib/jvm/java-8-oracle

 

that's the dockerfile for that image.

 

Yeah, that's basically what I did, but using 0.9.11. I guess that works because I've already downloaded that container.

 

But when I try your Dockerfile:

 

$ docker build --rm -t test .
Sending build context to Docker daemon  2.56 kB
Sending build context to Docker daemon
Step 0 : FROM phusion/baseimage:0.9.16
Pulling repository phusion/baseimage
INFO[0000] Get https://index.docker.io/v1/repositories/phusion/baseimage/images: x509: failed to load system roots and no roots provided

 

I also can't push an image

 

$ docker push coppit/filebot
The push refers to a repository [coppit/filebot] (len: 1)
Sending image list
FATA[0000] Put https://index.docker.io/v1/repositories/coppit/filebot/: x509: failed to load system roots and no roots provided

Can anyone running 6.0-rc3 confirm that they can "docker pull" some image that they don't already have?

Huh. Stopping and restating the Docker daemon from settings did the trick.

And now it's back, and no amount of stopping/starting fixes it.

 

I guess I'll start a thread in the bugs forum.

And now it's back, and no amount of stopping/starting fixes it.

 

I guess I'll start a thread in the bugs forum.

 

i'm betting that this is a docker hub issue and not an unraid one

It turns out the root cause was some old packages in my /boot/extra directory: http://lime-technology.com/forum/index.php?topic=40423.0