profile
viewpoint

Ask questionsName resolution failure when using Docker custom networks (swarm/compose)

From @gvancuts on March 1, 2018 20:55

Description of problem

Applications built using Docker Compose will fail if the services that compose it depend on name resolution to talk to each other.

Expected result

Docker Compose applications using name resolution would continue to work correctly.

Actual result

The services are not able to talk to each other. This can easily be reproduced by following stesp 1 to 4 of this Docker Compose Getting Started guide: https://docs.docker.com/compose/gettingstarted/. It works correctly if you use Docker with its default runtime (runc) but fails as soon as you switch to Clear Containers 3's runtime (cc-runtime).

Copied from original issue: clearcontainers/runtime#1042

kata-containers/runtime

Answer questions itsgk92

+1

useful!

Related questions

Pods stuck in ContainerCreating and Running hot 1
elasticsearch container fails to start due to `vm.max_map_count` too low hot 1
Issues starting container in VM when using virtio-fs, virtiofsd segfaulting hot 1
Unable to start docker in docker with virtio-fs hot 1
Firecracker: Fix slow bootup with Kata hot 1
Fail to deploy pod using kata-qemu on minikube when internetworking_model="tcfilter" hot 1
Kata support image booting via systemd hot 1
Attaching Physical NICs to Kata-Containers hot 1
Github User Rank List