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
With our current base image we have issues with DNS resolution. Our base image is using systemd/systemd-resolvd and this requires that /etc/resolv.conf be symlinked to /run/systemd/resolve/stub-resolv.conf . However, when using docker/buildkit/kaniko its not possible to make changes to resolv.conf as this is treated specially.
We are working around this issue temporarily by using bootcmd in cloud-init to run ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf when flintlock is called from capmvm.
However, we need a long term solution where the container image is setup correctly for dns resolution.
The text was updated successfully, but these errors were encountered:
With our current base image we have issues with DNS resolution. Our base image is using systemd/systemd-resolvd and this requires that
/etc/resolv.conf
be symlinked to/run/systemd/resolve/stub-resolv.conf
. However, when using docker/buildkit/kaniko its not possible to make changes to resolv.conf as this is treated specially.We are working around this issue temporarily by using
bootcmd
in cloud-init to runln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
when flintlock is called from capmvm.However, we need a long term solution where the container image is setup correctly for dns resolution.
The text was updated successfully, but these errors were encountered: