Comment 3 for bug 1692111

This is an interesting problem. So there are two strategies:

- When LXC adds an additional {G,U}ID mapping we could check whether this would lead to more than 5 mappings being requested. And while I sympathize with that I also dislike the fact that the in-kernel limit is arbitrary and I'm not sure if we want to hardcode something that might change at any point. However, we could maybe print the requested mapping count as debug info to the log.
- We find a workaround to only use the mapping for the host {G,U}ID in certain operations where it is required that this {G,U}ID is mapped. I need to think about that.