### Bug Description i was following [this](https://documentation.ubuntu.com/rockcraft/en/stable/tutorial/go/) tutorial (although i don't believe it matters greatly for this bud) and i've run into a version of [this](https://github.com/containers/podman/issues/12715) podman bug when trying to run the resulting container: ``` $ podman run -it --rm -p8000:8000 oci-archive:go-hello-world_0.1_arm64.rock Getting image source signatures Copying blob 841279616ebc done | Copying blob e472a184e3eb done | Copying blob 81c94c29611d done | Copying blob 3b8971000cc7 done | Error: writing blob: adding layer with blob "sha256:841279616ebc8b7deb83e501b434f67f18368258912eb212420a72fd446d0688"/""/"sha256:f4284345883ed8b365fb5fd46e2ccf6b46cafbd8d4301db5a990531b61f11b74": unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 584792:584792 for /app): Check /etc/subuid and /etc/subgid if configured locally and run "podman system migrate": lchown /app: invalid argument) ``` a bit of search led me to find that the culprit 584792 is the hardcoded `_daemon_` user in the pod. i've resolved the bug with ``` ME=$USER sudo -E bash -c 'echo "$ME:100000:584792" | tee /etc/subgid /etc/subuid > /dev/null' && \ sudo rm -rf $HOME/.local/share/containers/storage \ && podman system migrate ``` but i thought its worth knowing that default podman uid/gids are (or, at least, *can be*) outside of the default podman range. might be worth adding something to docs and/or allowing rockcraft to change the `_daemon_` id..? ### To Reproduce see above ### Environment - rockcraft 1.12.0 - no multipass - lxd 6.4 - ubuntu 25.04 - xps 13 8345 arm - kernel 6.14.0 - podman 5.4.1 ### rockcraft.yaml ```yaml name: go-hello-world # see https://documentation.ubuntu.com/rockcraft/en/1.12.0/explanation/bases/ # for more information about bases and using 'bare' bases for chiselled rocks base: bare # as an alternative, a ubuntu base can be used build-base: ubuntu@24.04 # build-base is required when the base is bare version: '0.1' # just for humans. Semantic versioning is recommended summary: A summary of your Go application # 79 char long summary description: | This is go-hello-world's description. You have a paragraph or two to tell the most important story about it. Keep it under 100 words though, we live in tweetspace and your description wants to look good in the container registries out there. # the platforms this rock should be built on and run on. # you can check your architecture with `dpkg --print-architecture` platforms: # amd64: arm64: # ppc64el: # s390x: # to ensure the go-framework extension functions properly, your Go project # should have a go.mod file. Check the parts section for the selection of # the default binary. # see https://documentation.ubuntu.com/rockcraft/en/1.12.0/reference/extensions/go-framework # for more information. # +-- go_hello_world # | |-- go.mod # | |-- migrate.sh extensions: - go-framework # uncomment the sections you need and adjust according to your requirements. # parts: # go-framework/install-app: # # select a specific Go version. Otherwise the current stable one will be used. # build-snaps: # - go/1.22/stable # organize: # # if the main package is in the base directory and the rockcraft name # # attribute is equal to the go module name, the name of the server will # # be selected correctly, otherwise you can adjust it. # # the file in /usr/local/bin/ with the name of the rockcraft project will be # # the binary to run your server. # # you can also include here other binary files to be included in the rock. # bin/otherbinary: usr/local/bin/projectname # go-framework/assets: # stage: # # by default, only the files migrate, migrate.sh, templates/ and static/ # # are copied into the image. You can modify the list below to override # # the default list and include or exclude specific files/directories # # in your project. # # note: Prefix each entry with "app/" followed by the local path. # - app/templates # - app/static # - app/otherdirectory # - app/otherfile ```