How can my Forgejo runner access volumes from a Docker-in-Docker setup?

It sounds like you're encountering some common volume binding issues. One thing to consider is that when you set up-volumes, you might accidentally overwrite what's already there. Instead of trying to map everything to the runner, think about storing your artifacts in Forgejo after the build process. Depending on the type of artifact—like if it's an image, use a registry; for binaries or executables, you might want to store them in object storage or directly in Forgejo. This approach could make it easier to manage and retrieve your builds later.

Yeah, I had the same issue before! Just moving stuff around in directories can get tricky. If you're dealing with persistent storage, make sure the mappings are correct. Also, don't forget that the artifact type might influence the best storage method—maybe storing it directly in Forgejo could save you some headaches.