crc: Installing CRC breaks `docker build`

Last steps:

Expected behavior:

  • docker build has network access.

Actual behavior:

  • docker build fails due to network issues.

Workaround:

  • Remove all files containing crc in the file name from /etc/NetworkManager
  • Reload network manager – sudo systemctl reload NetworkManager
  • Restart docker – sudo systemctl restart docker

System:

Linux XXX 3.10.0-957.10.1.el7.x86_64 #1 SMP Thu Feb 7 07:12:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Docker:

$ docker version
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-96.gitb2f74b2.el7.x86_64
 Go version:      go1.10.8
 Git commit:      b2f74b2/1.13.1
 Built:           Tue Apr  2 21:01:07 2019
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-96.gitb2f74b2.el7.x86_64
 Go version:      go1.10.8
 Git commit:      b2f74b2/1.13.1
 Built:           Tue Apr  2 21:01:07 2019
 OS/Arch:         linux/amd64
 Experimental:    false

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 4
  • Comments: 22 (13 by maintainers)

Most upvoted comments

I faced with this issue too. It would be nice for development flow to have crc and docker working both and in the same time on the working laptop.

CRC would work, but you filed an issue related to docker build failing. And this is due to the fact how ‘docker’ interprets a 127.0.0.1 entry in /etc/resolv.conf. This is not something we can handle here… but would have to be filed against the upstream.

Note: since NetworkManager with the installer and CRC uses dnsmasq=true it will use 127.0.0.1 as first entry in /etc/resolv.conf. It is Docker that replaces this with 8.8.8.8. Since you are on the RH network, this nameserver is blocked. See: https://github.com/moby/moby/issues/6388