Skip to content
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

Puter docker container cannot start, write to /var/puter #694

Open
1 of 4 tasks
mfrancisbeehive opened this issue Aug 16, 2024 · 5 comments
Open
1 of 4 tasks

Puter docker container cannot start, write to /var/puter #694

mfrancisbeehive opened this issue Aug 16, 2024 · 5 comments

Comments

@mfrancisbeehive
Copy link

mfrancisbeehive commented Aug 16, 2024

Issue Description

Docker compose not working on Mac. Says it cannot write to /var/puter

Steps to Reproduce

  1. Create a new directory to hold puter files
  2. Change to the directory
  3. Paste and run the commands from the README for Docker Compose on Mac/Linux

Expected & Actual Behavior

Puter should start and run as normal

Addition Information or Screenshots (if applicable)

Captura de pantalla 2024-08-16 a la(s) 11 59 55 a m

Deployment

  • Production (puter.com)
  • Development (npm run start)
  • Docker (via docker run)
  • Docker (via docker-compose)

Puter version (if accessible)

Latest as of this issue submission

@KernelDeimos
Copy link
Contributor

Hello, I'm not able to reproduce this issue. Please ensure you're running docker compose up in the correct directory - a directory containing a subdirectory puter with the sub-directories data and config.

Also you may want to know that running with docker compose currently comes with a disadvantage. The development console gets completely obliterated by Docker and you will be unable to get the password for the admin user or run any dev console commands.

@Roi-Danton
Copy link

Roi-Danton commented Aug 26, 2024

I have the same problem.
Did a fresh installation.

There are two options described how to do puter with docker.
None of them worked for me.

@DevBengel
Copy link

Same here- i mounted two new docker volumes to puter. Same result. Its a permission issue. If you really chown the directories and/or volumes like stated (chown -R 1000:1000 puter) you are allowed to write.
This is just a workaround in my opinion...

Best regards

@Roi-Danton
Copy link

Nope, this doesn't work for me.
I tried every right I know.
The UID 1000 is set in the yml file right?
Because 1000 is another user for me. Not the one running the container.

@dennysubke
Copy link

Same here- i mounted two new docker volumes to puter. Same result. Its a permission issue. If you really chown the directories and/or volumes like stated (chown -R 1000:1000 puter) you are allowed to write. This is just a workaround in my opinion...

Best regards

Didn't work for me... It's frustrating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants