-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Bug: Puter won't start anymore #1081
Comments
Works with |
What version were you running before? Or, are you using the latest changes on |
I've been running on |
Apparently it does, that's interesting. I'm at a bit of a loss for what causes this error, but of the |
I don't do anything inisde the container, I just start it :) Just remembered and checked: the container image builds on every push to main. |
@KernelDeimos I get the same problem with 2.5.0 now |
Also, I can't run |
So, I've done a
I'm wondering if the |
I can't get the Docker image to build with the Dockerfile, for some reason. Trying to figure out why that is. |
Here's what I know so far:
The remaining questions right now are:
I'll keep this thread updated as I learn more. |
I think I found the source of the issue:
The Next I'm going to try to find out:
|
Okay bad news, it still doesn't work. I'm going to make SNSService import lru-cache in a more flexible way so that both versions will work, but I really don't like this solution because getting the wrong version of lru-cache should never happen in the first place. I'm going to try more research and communication with other developers and see if I can get to the bottom of this. |
|
Running |
Wow, that's a lot of messages :-) I can verify that building the image locally also results in the same error, so it's something in the Docker image build that goes haywire... |
Ran into this error with 23-bookworm:
On search, that led me to this comment: nodegit/nodegit#2006 (comment) Now trying with 20-bookworm and 20-alpine |
I'm getting a successful build on node20-alpine with the additional
|
Acutally, the latest The GUI doesn't fully work, but it's better than it was :) |
Issue Description
I run puter via Docker, but it doesn't work anymore.
Not entirely sure when this happened, but this what happens:
Steps to reproduce
Use
docker compose
to run:main
branch of puterExpected behaviour
I expect it to work :)
Addition Information or Screenshots (if applicable)
No response
Deployment
npm run start
)docker run
)docker-compose
)Puter version
No response
The text was updated successfully, but these errors were encountered: