-
Notifications
You must be signed in to change notification settings - Fork 23
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
Python problems when deploying the container fresh #80
Comments
For me, a workaround would be to set I don't know exactly why this happens, but most likely there being a bug somewhere in the init process |
Hey @hydrogendos! I came across the same issue, and wanted to run these steps. Where did you get the |
same issue here |
My apologies for the lack of maintenance and the vast amount of bugs. |
Thank you for your honesty
…On Sun, 14 May 2023, 15:15 JVT038, ***@***.***> wrote:
My apologies for the lack of maintenance and the vast amount of bugs.
I have been struggling to find sufficient motivation to fix these issues,
and I can't promise anything.
I'll try to fix this and close these issues.
—
Reply to this email directly, view it on GitHub
<#80 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFL5IW76GSVISTCIYVJPLLXGDLHDANCNFSM6AAAAAAVDQB7MM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
When I set up Metatube completly fresh, I experienced this error and couldnt figure out why it comes up.
I used this docker run command:
This is the error message I always got:
I hope you can help me find my mistake, thanks
The text was updated successfully, but these errors were encountered: