Matt Heon

@flouthoc PTAL

We do not use the host's DNS, but the container's DNS, which defaults to the same nameservers as the host. Setting container default DNS servers in containers.conf ought to do...

...Did we not implement that yet? Because that was definitely in the original design doc.

Well, we have a session later today about new functionality, we can add this to it.

I might do a `podman system` command here that wraps around `podman start` instead (I dislike adding really-specific options to common commands) but the general approach is a thumbs-up from...

Not true, Podman has included restart policies for some time (I think we added it in the 1.4.x releases?)

Manual operations would still work (`podman kill` would hit the OCI runtime and kill the container, for example), but we would not be able to retrieve exit code. More serious...

Worth noting that this can potentially be used to obfuscate other malicious actions in the container - by killing Conmon, all logging of the container is also stopped.

This repo (and dnsname) are deprecated. We've switched all development efforts over to the Netavark network stack. @Luap99 @baude Should we consider archiving this repo?

@flouthoc PTAL