Valentin Rothberg

@stevvooe Thanks a lot for your comments. > @vrothberg Any reason we just don't accept these in the --registry-mirrors flag? What is the reasoning behind the separate flag? We figured...

> @vrothberg That is my question: is there a difference in behavior or policy, other than that these registries may need separate credentials? @stevvooe No, to my knowledge, there is...

> @vrothberg So, do you think a separate flag is really necessary? @stevvooe No, not from a technical point of view. I prefer a separate flag because it is more...

@stevvooe, @thaJeztah I'd love to push this PR forward. As far as I can see, the remaining open question is whether a dedicated flag for private-registry mirrors is really needed...

> @vrothberg I just LGTM'd #34495. > Do you have an example of the flag format? Thanks a lot, @stevvooe! In case we merge the semantics of private-registry mirrors with...

@thaJeztah, @stevvooe: First, thanks a lot for your valuable feedback. Unifying and reworking the registry-related configuration makes a lot of sense. Although such a change won't be backwards compatible, we...

> How about show private registry infos via docker info command? @shyr That's a great idea. We'll definitely look into this. @stevvooe If you find time, would you provide feedback...

Thanks for reaching out, @Vogtinator! I suggest to wait a bit more on https://github.com/iovisor/gobpf/pull/311. We may need to prioritize getting https://github.com/containers/oci-seccomp-bpf-hook/issues/93 done. Cc: @saschagrunert

Thanks for the ping! I am OK vendoring a non-release commit.

Thanks for reaching out! Can you share the output of `podman info` and which version of the hook you are using? Usually such hiccups are kernel bugs but I can't...