Snap won't build due to permission error

Hey,

a snap of one of my projects randomly stopped building, I haven’t played with the permissions, not have I messed with my snapcraft / snapd installation afaik.

Can anyone tell me what’s going on here?

~/code/cordless (master)$ SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=y snapcraft --debug
Starting snapcraft 3.8 from /snap/snapcraft/3440/lib/python3.5/site-packages/snapcraft/cli.
snapcraft is running in a docker or podman (OCI) container
Parts dir /mnt/data/code/cordless/parts
Stage dir /mnt/data/code/cordless/stage
Prime dir /mnt/data/code/cordless/prime
snapcraft is running in a docker or podman (OCI) container
Parts dir /mnt/data/code/cordless/parts
Stage dir /mnt/data/code/cordless/stage
Prime dir /mnt/data/code/cordless/prime
Launching a VM.
Running multipass start snapcraft-cordless
                                                                                                                                                                                                                     snapcraft is running as a snap True, SNAP_NAME set to 'snapcraft'
Running multipass exec snapcraft-cordless -- sudo -i env SNAPCRAFT_HAS_TTY=True printenv HOME
Running multipass exec snapcraft-cordless -- sudo -i env SNAPCRAFT_HAS_TTY=True snapcraft snap
[Errno 1] Operation not permitted: 'snap/snapcraft.yaml'
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]: n
Running multipass exec snapcraft-cordless -- sudo -i env SNAPCRAFT_HAS_TTY=True test -f /tmp/snapcraft_provider_traceback
Running multipass copy-files snapcraft-cordless:/tmp/snapcraft_provider_traceback /tmp/snapcraft_provider_traceback.12403
Running multipass exec snapcraft-cordless -- sudo -i env SNAPCRAFT_HAS_TTY=True rm /tmp/snapcraft_provider_traceback
Running multipass exec snapcraft-cordless -- sudo -i env SNAPCRAFT_HAS_TTY=True /bin/bash

Regards Marcel

Can you try running snapcraft --destructive-mode instead of just snapcraft in this environment?