Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

1.4.0-dev (41c9f66b68968988f4eec21c220a6dba19497596) - error with symlinked /etc/resolv.conf #87

Open
Radtoo opened this issue Jan 3, 2022 · 0 comments

Comments

@Radtoo
Copy link

Radtoo commented Jan 3, 2022

I am not entirely sure if this is fully a bug in dnsname or an interaction with podman-compose but there is an error when /etc/resolv.conf is a symlink (in my case /etc/resolv.conf -> /var/run/connman/resolv.conf).

The error goes away by substituting the symlink with the linked resolv.conf itself, but symlinks probably should be permitted, some setups like mine require them to work properly.

ERRO[0000] error loading cached network config: network "s-docker_default" not found in CNI cache
WARN[0000] falling back to loading from existing plugins on disk
Error: unable to start container cfb155858becfbc872c358f14206011cb29a6a67b81c991a027a660c481b1705: error configuring network namespace for container cfb155858becfbc872c358f14206011cb29a6a67b
81c991a027a660c481b1705: error adding pod s-docker_filer_1_s-docker_filer_1 to CNI network "s-docker_default": dnsname error: dnsmasq failed with "\ndnsmasq: directory /etc/resolv.conf for resolv-file is missing, cannot poll\n": exit status 5
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant