-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Changing system timezone breaks container #96
Comments
I have the same problem after changing the time. "error creating container: exit status 1" I don't know how to resolve this. |
I fixed it with a simple Maybe that should be triggered automatically in a save way. |
I just tried your suggestion. It does make the container work again, but it does so by re-initializing it, deleting all installed packages, changes etc. in the process. I don't think it should be used as a fix, but rather as a last resort if we can't find a better solution. |
I would like to add that after reinitializing the container, I tried to reproduce the error by changing the system time/timezone, but to no avail. Maybe the problem only presents itself if the wrong timezone is chosen during install? |
I had the same problem, this re-init worked |
Strange, this was my experience as well. I was sure I had picked the correct timezone on install, but later on I discovered the clock was wrong so I thought I had made a mistake and corrected the timezone. That's when the container stopped working. Maybe this is a problem with the install process in Vanilla and not related to apx? |
I changed the system timezone on my fresh VanillaOS install and was no longer able to enter the default container, being met with the following message.
Error: OCI runtime error: unable to start container "8a99d8ffdf38fba65f173f069bc0adb567edac94037f0525dfaecc3b6176ce8f": mount
/etc/localtime
to/etc/localtime
: Not a directoryThe text was updated successfully, but these errors were encountered: