4 ms·
Yes, just start from scratch and provide uid-mappings from the beginning. Looks like those uids were set from before adding the mappings and it is trying to acc
by Helmut10001 3y ago
Yes, just start from scratch and provide uid-mappings from the beginning. Looks like those uids were set from before adding the mappings and it is trying to access uids it is not allowed to access.
I used rootless docker in rootless lxc because the Postgres Docker (e.g.) will try to setup a non-root user by default. In a rootless LXC, this means it will try to access very large uids (>100000), which are not available, unless explicitly prepared.
- dusanh 3y agoThat actually did not do anything different for me. I did the following: 1) Created a new LXC. 2) As root, I created a new user "devel" 3) For the "devel" user set both subuid and subgid to devel:100000:65536 4) As root, installed podman 5) In another SSH session, logged in as "devel" and ran "podman version" Same error as before. This is in a Debian 12 LXC running on Proxmox.
- Helmut10001 3y agoI am also using Docker in Debian 12 LXC on Proxmox. I am not sure what has gone wrong here.
- dusanh 3y agoWas there anything extra you have done on the Host itself?
- Helmut10001 3y agoI described the full process here [1]. The only thing that seems to differ is podman for you. Ah, I see: > 4) As root, installed podman I installed docker as the non-root user. See my Mastodon post, there's a specific procedure to install Docker in a user namespace ("devel" in your case). [1]: https://du.nkel.dev/blog/2021-03-25_proxmox_docker/ https://du.nkel.dev/blog/2021-03-25_proxmox_docker/