For building my app as a snap, I used to have a Docker image which I can use in my CI/CD pipelines. I maintain a repository to build the image on GitLab: https://gitlab.com/rpdev/docker/snapcraft The resulting Docker image is used in this project: https://gitlab.com/rpdev/opentodolist Initially, this worked quite fine and allowed immediate feedback when the Snap build would ever break. However, some weeks ago something must have changed upstream. I first thought that maybe my Dockerfile had an issue, so I migrated it to the "official" one from here: https://github.com/snapcore/snapcraft/tree/master/docker However, with both the upstream Dockerfile as well as my own one (which basically is inspired by the upstream one) I get the following error when running snapcraft within the container later on in the CI/CD pipelines (e.g. in this job -> https://gitlab.com/rpdev/opentodolist/-/jobs/1934812717): $ snapcraft snap Traceback (most recent call last): File "/snap/snapcraft/current/bin/snapcraft", line 5, in <module> from snapcraft.cli.__main__ import run ModuleNotFoundError: No module named 'snapcraft' I tried to look for a possible solution and found the following forum post: https://forum.snapcraft.io/t/snapcraft-failed-in-container/27921/2 I applied the suggested patch in the Dockerfile, but still get the same error. So it seems to me something changed upstream and completely broke using snapcraft within docker. Doing some further research, I think I am not the only one affected, see e.g. this issue on GitHub: https://github.com/cibuilds/snapcraft/issues/36 It would be really great if this could be fixed (because IMAO it is better to have the possibility to integrate the snap build directly with my project pipelines) or if this change is intentional, it should at least be properly documented (I think, it should be reflected here: https://snapcraft.io/docs/build-on-docker). Thanks for considering!