-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to bootstrap the container on macOS Ventura 13.5.2/13.6.0 #391
Comments
If I change the command below, different exception throwed:
|
All the env variables are written to /config/icloudpd.conf and then loaded from there, it's possible the logic is off for force_gid. Try recreating your container without any env variables then editing that file to force_gid=true |
Correct. I also figured out. But even with the force_gid properly configured, the script still fail as my second comment.
Within my container environment, this command eventually got translated into:
The thing is, if I log into the container via terminal as inside root, then the Why and how to fix? Thanks & regards |
Great work. I should be able to fix this now you've found the root cause. Hopefully I'll be able to take a look at this later today. |
Now I believe the issue is really at line 833. cause the below error occurred right before calling ConfigurePassword:
Indeed, inside the container, the /config/ folder belongs to both <my_host_user> and <my_host_group> exists inside the container after container creation. |
In fact, looks like the And here is my docker run command and parameters:
icloudpd.conf with privacy info removed:
|
I just realized the underlying podman might be the real cirminal here... |
Switched to orbstack, now the initialization run through flawlessly. |
Description:
I am trying to deploy the docker-icloudpd on a macOS server for downloading multiple users' photos timely.
And the container launch failed as below:
I don't understand why the script says the force_gid is False even it was already explicitly set to True
The text was updated successfully, but these errors were encountered: