You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: