flannel fails with "Unable to find image 'quay.io/coreos/flannel:0.4.0' locally"

[gnresende]

Hi all,

I'm trying to start the flannel in my lab environment and getting the following messages:

Aug 15 08:52:30 vmnode1 systemd[1]: Starting Network fabric for containers...
Aug 15 08:52:30 vmnode1 sdnotify-proxy[616]: Unable to find image 'quay.io/coreos/flannel:0.4.0' locally
Aug 15 08:52:30 vmnode1 sdnotify-proxy[616]: time="2015-08-15T08:52:30Z" level=fatal msg="Error response from daemon: v
Aug 15 08:52:30 vmnode1 systemd[1]: flanneld.service: main process exited, code=exited, status=1/FAILURE
Aug 15 08:52:30 vmnode1 systemd[1]: Failed to start Network fabric for containers.
Aug 15 08:52:30 vmnode1 systemd[1]: Unit flanneld.service entered failed state.



Aug 15 10:02:39 vmnode1 systemd[1]: flanneld.service: main process exited, code=exited, status=1/FAILURE
Aug 15 10:02:39 vmnode1 systemd[1]: Failed to start Network fabric for containers.
Aug 15 10:02:39 vmnode1 systemd[1]: Unit flanneld.service entered failed state.
Aug 15 10:02:39 vmnode1 systemd[1]: flanneld.service failed.
Aug 15 10:02:39 vmnode1 sdnotify-proxy[20213]: time="2015-08-15T10:02:39Z" level=fatal msg="Error response from daemon: v1 ping attempt failed with error: Get https://quay.io/v1/_ping: dial tcp: lookup quay.io: Temporary failure in name resolution. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry quay.io` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/quay.io/ca.crt"


I think that this is occurring why flannel depends on early-docker (it is a container) and in my environment I need to set a HTTP_PROXY (and HTTPS_PROXY) to allow docker to access internet.

There is any workaround?

Thanks in advance.

[eugene.y...@coreos.com]

Yes, I believe this is because you don't have access to the Internet. You will need to create a systemd drop-in file that you can write out in your cloud-config like so:

#cloud-config

coreos:

  units:

    - name: early-docker.service

      drop-ins:

        - name: 10-http-proxy.conf

          content: |

              [Service]

              Environment=HTTP_PROXY="http://my.http-proxy.com"

-Eugene

[gnresende]

Hi Eugene,

Thank you for your help.

I tried it in cloud-config (user_data) and the file was generated but don't solve the problem. I don't mentioned in my previous message but I already tried it on flanneld.service and don't do the job.

vmnode1 early-docker.service.d # cat 10-http-proxy.conf
[Service]
Environment=HTTP_PROXY="http://192.168.56.1:3128"
Environment=HTTPS_PROXY="http://192.168.56.1:3128"
vmnode1 early-docker.service.d # pwd
/etc/systemd/system/early-docker.service.d

and the same error (even with some reboot):

Aug 15 10:14:20 vmnode1 systemd[1]: Starting Network fabric for containers...
Aug 15 10:14:20 vmnode1 systemd[1]: flanneld.service: main process exited, code=exited, status=1/FAILURE
Aug 15 10:14:20 vmnode1 systemd[1]: Failed to start Network fabric for containers.
Aug 15 10:14:20 vmnode1 systemd[1]: Unit flanneld.service entered failed state.
Aug 15 10:14:20 vmnode1 systemd[1]: flanneld.service failed.
Aug 15 10:14:20 vmnode1 sdnotify-proxy[666]: Unable to find image 'quay.io/coreos/flannel:0.4.0' locally
Aug 15 10:14:20 vmnode1 sdnotify-proxy[666]: time="2015-08-15T10:14:20Z" level=fatal msg="Error response from daemon: v


Some other possible solution?

Thanks in advance.

[gnresende]

Hi Eugene,

I'm sorry. I found an erro in my configuration. Your solution solve the problem.

Thank you!!

[Jason Tower]

i'm having the same problem (my cluster is behind a http proxy and flanneld fails because "Unable to find image 'quay.io/coreos/flannel:0.5.3' locally"

can you post your cloud config file?  mine looks like this, dockers works fine with the proxy server but flanneld doesn't.

  units:
    - name: docker.service
      command: start

      drop-ins:
        - name: 10-http-proxy.conf
          content: |
            [Service]

            Environment="HTTP_PROXY=http://172.18.192.5:8080"
            Environment="HTTPS_PROXY=http://172.18.192.5:8080"
    - name: flanneld.service
      command: start
      drop-ins:
        - name: 50-network-config.conf
          content: |
            [Service]
            ExecStartPre=/usr/bin/etcdctl set /coreos.com/network/config '{ "Network": "10.2.0.0/16" }'
            Environment="HTTP_PROXY=http://172.18.192.5:8080"
            Environment="HTTPS_PROXY=http://172.18.192.5:8080"

[Nick Owens]

jason,

you need to apply the proxy configuration to 'early-docker.service', which is used to actually run flannel, so that it is started before the real docker.service. please apply your proxy configuration to both early-docker.service and docker.service and see if that fixes the issue.

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason Tower]

it most certainly did fix the issue, thanks very much nick!