This is not what I meant. You still have volumes mounted on the local machine:
-v $PWD:/build -v $PWD/srtool-out:/out -v srtool-cache:/home/builder/cargo
I was thinking about letting docker manage its volume and build the runtime inside and then fetch the result (binary, hash…) from the inside of the container. But I have to take a docker lesson with you in particular for network and volumes part.
You’re right, this is not what you meant. This proposal aims to solve the permission problem when using srtool to check the wasm runtime hash.
I’m not sure what you want to accomplish by preventing bind volume usage, but for the use case above, sticking to bind volumes and dealing with permissions inside the container is simpler (in my opinion).
You’re welcome. It would be more efficient to discuss this in audio. Please suggest me a slot for an evening call in the next days.