unable to `emerge --sync` in a fresh container about gentoo-docker-images

[ajakk]

This smells like you're omitting some configuration or something, but, you're not supposed to emerge --sync in a container anyway. See the README for repo usage.

[asarubbo]

I understand you concern, but I really don't understand why to use portage I'm forced to use another container considering that it always worked for me in the past...

Anyway emerge --info works out of the box in whatever clean stage3 we have, I don't understand why you think I'm missing configuration or something....and btw what you mean by something?

[asarubbo]

In any case it works on the musl container ( like reported on #125 ), so I'm pretty sure that there is something nasty here

[ajakk]

Without being able to reproduce, it's very hard to be able to do anything.

[asarubbo]

Can you try on an up-to-date CentOS 7 ?

I can reproduce all time so I suppose you can hit this issue too.

[asarubbo]

privileged container works for me.

For the record I have a working Dockerfile that run emerge --sync. I don't use it every day but I can confirm that it worked at least on 2022-03-24 where I have generated an image.