Paul Holzinger
Paul Holzinger
These linters provide helpful warnings to write better error assertions in case tests fail. Right now there are a lot of report errors with them.
I am currently trying to shrink the podman binary size. Looking through all dependencies I see that `github.com/jinzhu/copier` is only used a single time. While this package is only 204...
When calling Save() from the podman API using file paths as parameter requires us to write a temporary file, this is bad since the API then needs to read it...
Reading the signature code I noticed that the user policy json file is always read from ~/.config and does not honour the XDG_CONFIG_HOME env var. https://github.com/containers/image/blob/bdfde4d38cfcaaa3bba082c8fe8a5f6f33fed7a3/signature/policy_config.go#L37 https://github.com/containers/image/blob/bdfde4d38cfcaaa3bba082c8fe8a5f6f33fed7a3/signature/policy_config.go#L67 AFAICT the rest...
Follow up to commit eaf60c7fe7, lets see how bad things are going to break. #### Does this PR introduce a user-facing change? ```release-note None ```
disable linters: - mnd (magic number checker): it seems to complain about almost anything, while there might be a few valid findings most of them are useless - canonicalheader: HTTP...
The image is way to big (over 800MB) that slows tests down as we always have to pull this, the tests itself are also super slow due the entrypoint logic...
There are some basic problem with our hosts and resolv.conf handling when we the pasta network mode is used. For resolv.conf unless custom dns servers are specified via config or...
When running inside of unprivileged containers /proc is normally mounted read only. Now if a users tries to run netavark it will fail hard if we cannot set all the...