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
Docker image is misconfigured #375
Comments
Looks like issue 3 should have been fixed by #342 but the docker images haven't been built with that. Date wise for me, it was merged on April 24th, and the latest release and latest docker image were on April 23rd. That docker image claims to be 2.1.1, but maybe the internal version number just didn't get updated? As a side note, it'd be good if the docker images were named/tagged/whatever to say what release version they are. |
Carrying on from #350 because this is a different issue than the one originally reported.
I am absolutely not a Docker expert, so I am fumbling my way through this, but from setting up Puter with the recommended Docker Compose installation steps I have a few issues, or possible issues:
chmod 777
on the docker puter directory, otherwise it couldn't start because it failed to write to/var/puter
.npm install
from inside the container fixes this, so... somehow we're not running the postinstall. I've confirmed this still occurs with the most recent package.latest
isn't the latest, it's v2.1.0, and there have been no releases at all for 2 weeks.The text was updated successfully, but these errors were encountered: