5:20 a.m.
On 8/2/23 10:50, Chris Evich wrote:
On 8/1/23 17:18, Daniel Walsh wrote:
> There used to be a max ranges of 5 and Podman might not allow you to
> specify that many.
>
> Anyways why worry about individual ranges. Just define cevich with
> 100000000 UIDs and go to town.
The reason to define multiple ranges (one per pod/app) is, it may be
easier to codify the individual ranges in orchestration tools like
Ansible. Either way you do it, it seems there's a risk of
accidentally use overlapping IDs across pods/apps. IIUC, having
multiple entries defined would offer some protection against that.
It's okay there's some entry limit, I s'pose it's even helpful. If
you're managing "too many" separate ranges, it's probably a sign you
should at least be using kube YAML if not minikube or full-blown kube
rather than trying to stuff everything into generic tooling like
Ansible. Or (shock) trying to manage a complex setup by hand.
Sure, but Podman has smarts about currently used ranges and can use
minimal ranges based on the image in use. If you use something like
Ansible then it may or may not know about existing containers, and
ranges in use, as well as would need to use 65k per container.
---
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If there's a "hard-way", I'm the first one to implement it.
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io