Matt Heon comments

Results 59 comments of


Matt Heon

containers do not start after reboot while dnsname enabled

Are these containers using static IPs, by chance?

containers do not start after reboot while dnsname enabled

Alright, does not sound like anything I'm familiar with, then. @baude Mind taking a look?

Podman log file max size limit not working

Can you do a `podman run --log-level=debug` command with this field set in `containers.conf` (image and command don't matter, just need to run a container) and provide the full output?...

Podman log file max size limit not working

We're sending `--log-size-max 10` to Conmon. That looks correct? @haircommander PTAL

Shall we lookup host's /etc/hosts before forwarding other request to host's /etc/resolv.conf?

This sounds like an information leak - would allow containers to see information about the host that they otherwise could not. Potentially a security risk, so I'm rather leery about...

coredns: response message always set recursion available (`RA`) when `RD` is set in request

One nit otherwise LGTM

coredns: response message always set recursion available (`RA`) when `RD` is set in request

CI seems broken, but it doesn't look like your PR; could be a more general thing?

coredns: do not combine results of `A` and `AAAA` records when query type only requests specific result.

LGTM once you get the tests fixed

coredns: do not combine results of `A` and `AAAA` records when query type only requests specific result.

There a reason this still has a hold on it?

container.podman.podman_image: newline character appended to directory path causing => Error: context must be a directory

If Ansible is responsible for adding the newline, you'd probably be better off filing an issue against the Ansible Podman collection.