Ubuntu Docker Desktop changing file Owner after running

[RunTheGambit]

Issue:

• After running the Docker image, the owner and group of the Temp folder changes to 100999. See below:
• 
• Ran chown and chmod to change ownership back to myself and was able to access temp and upload more files.
• Unfortunately every file that was processed had its ownership changed as well.

Configurations:

• Docker Desktop 4.15.0 [(93002)] Following the instructions here
• Setup openPGP for password management as per the instructions here
• Ubuntu 22.04.1 LTS (64bit)
• UID 1000 / GID 1000
• User added to Docker group / rootless mode

Thoughts/Questions

• Docker Desktop runs a VM and describes a similar situation here. I followed the instructions shown and confirmed both /etc/subuid and /etc/subgid show the expected information. What I am unsure about how to perform is the last line here:

The problem is resolved by creating a group with the new GID and adding our user to it, or by setting a recursive ACL (see setfacl(1)) for folders shared with the Docker Desktop VM.

• In the Auto-m4b documentation on creating the docker-compose file, you enter the path to the config folder. I created a folder in the same directory as temp which is where the auto-m4b-tool.log exports to. Does that need to map to a different config folder in docker or on the system?
• Could it be an issue with openPGP?
• The Auto-m4b container logs have errors at initialization that may help?

2023-01-05 13:02:36 *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2023-01-05 13:02:36 *** Running /etc/my_init.d/10_syslog-ng.init...
2023-01-05 13:02:38 *** Booting runit daemon...
2023-01-05 13:02:38 *** Runit started as PID 22
2023-01-05 13:02:38 New password: Password change aborted.
2023-01-05 13:02:38 passwd: Authentication token manipulation error
2023-01-05 13:02:38 passwd: password unchanged
2023-01-05 13:02:38 Use of uninitialized value $answer in chop at /usr/sbin/adduser line 591.
2023-01-05 13:02:38 Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 592.
2023-01-05 13:02:37 Jan 5 18:02:37 594e178ce787 syslog-ng[14]: syslog-ng starting up; version='3.25.1'
2023-01-05 13:02:38 Jan 5 18:02:38 594e178ce787 cron[27]: (CRON) INFO (pidfile fd = 3)
2023-01-05 13:02:38 Jan 5 18:02:38 594e178ce787 cron[27]: (CRON) INFO (Running @reboot jobs)
2023-01-05 13:02:38 Adding user autom4b' ... 2023-01-05 13:02:38 Adding new group autom4b' (1000) ...
2023-01-05 13:02:38 Adding new user autom4b' (1000) with group autom4b' ...
2023-01-05 13:02:38 Creating home directory /home/autom4b' ... 2023-01-05 13:02:38 Copying files from /etc/skel' ...
2023-01-05 13:02:38 Try again? [y/N] Changing the user information for autom4b
2023-01-05 13:02:38 Enter the new value, or press ENTER for the default
2023-01-05 13:02:38 Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] Created missing autom4b user with UID 1000
2023-01-05 13:02:39 Using 6 CPU cores as defined.
2023-01-05 13:02:39 Using 1m min sleep time.
2023-01-05 13:02:39 Making a backup of the whole /temp/recentlyadded/
2023-01-05 13:02:39 Making sure all books are in their own folder
2023-01-05 13:02:39 Moving folders with 2 or more audiofiles to /temp/merge/
2023-01-05 13:02:39 Nested subfolders are BAD moving to /temp/fix
2023-01-05 13:02:39 Moving single file mp3's to /temp/merge/
2023-01-05 13:02:39 Moving all the single m4b books to /temp/untagged/
2023-01-05 13:02:39 No folders detected, next run 1m min...
2023-01-05 13:03:39 Making a backup of the whole /temp/recentlyadded/
2023-01-05 13:03:39 Making sure all books are in their own folder
2023-01-05 13:03:39 Moving folders with 2 or more audiofiles to /temp/merge/
2023-01-05 13:03:39 Nested subfolders are BAD moving to /temp/fix
2023-01-05 13:03:39 Moving single file mp3's to /temp/merge/
2023-01-05 13:03:39 Moving all the single m4b books to /temp/untagged/
2023-01-05 13:03:39 No folders detected, next run 1m min...

Thank you in advance for any help you can offer!

[RunTheGambit]

This is a known issue with docker desktop.
I did a full uninstall of docker desktop and a fresh install of the docker engine.
Tested it today and had no permission issues