You can try running docker as pi (instead of root which is the default, and really should be the way to run it instead of straight out root), then the files will be owned by pi.
You can also see if your container can run (internally) as user pi, in which case the files will be owned by the pi user.
You can also modify your dockerfile.or compose file (if you're using docker compose) so the needed ownership/permissions are set up properly when the container starts.
There a quite a few different ways to handle this, but I know nothing about your container, how it works, was composed, etc, so you'll need to learn a few of those concepts and seem which one is best suited for your setup.
Best thing is to learn a little how docker runs and make it work however you want.
You can also see if your container can run (internally) as user pi, in which case the files will be owned by the pi user.
You can also modify your dockerfile.or compose file (if you're using docker compose) so the needed ownership/permissions are set up properly when the container starts.
There a quite a few different ways to handle this, but I know nothing about your container, how it works, was composed, etc, so you'll need to learn a few of those concepts and seem which one is best suited for your setup.
Best thing is to learn a little how docker runs and make it work however you want.
Statistics: Posted by memjr — Mon Jun 03, 2024 2:51 am