When running tests, py.test writes output files in the /src tree. When this tree is owned by a user with UID!=1000, this will typically fail.
As it seems, it is currently not easily possible to mount a volume via -v' and to apply UID mapping. As a simple workaround, I would propose to copy everything form/srcto some other location (or rename the mount point and copy to/src` ...) when the container is started. Read access should typically be possible, and it might be desirable to never modify the mounted source from within the container, anyhow.
When running tests, py.test writes output files in the /src tree. When this tree is owned by a user with UID!=1000, this will typically fail.
As it seems, it is currently not easily possible to mount a volume via
-v' and to apply UID mapping. As a simple workaround, I would propose to copy everything form
/srcto some other location (or rename the mount point and copy to
/src` ...) when the container is started. Read access should typically be possible, and it might be desirable to never modify the mounted source from within the container, anyhow.