-
-
Notifications
You must be signed in to change notification settings - Fork 584
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
Problem with docker-compose #516
Comments
OK, that sounds strange, I'll see if I can reproduce it. Yeah, the docker compose is focused on development at the moment. There is already a PR to make the code changes persist in a volume, but we're not there yet. You basically want an image that you can update regularly, right? |
Yeah, basically I want a stable build that I can quickly get up and running @rolandgeider |
I've started a new repo with only the docker-compose files to use for production-like environments: https://github.com/wger-project/docker People that don't want to develop, can just pull that and get started. |
@rolandgeider this is awesome, thank you so much! I would I go if I already had nginx running? Can I somehow map the wger port to a custom one? |
Yeah, you could just edit the port in the docker-compose.yml file. But be a bit patient, this is not working 100% yet! 😅 |
Yeah, no worries, I really appreciate the support! |
You can give it a try now if you want |
The original problem should be solved as well |
i have a similar problem. when i first build the wger/server:latest image (it built successfully, after some tweaks, see #1655 ), then trying to run it:
|
The issue is due to this flag when running the container:
inside the container, wger has user ID 1000. |
after some experimentation, i realized it would be a lot of work to try to cleanly support the use case of a different user ID, and since no one else is dealing with this, i just changed my own UID on my host to 1000. |
Hi, I am having some issues setting up wget with docker-compose.
What I did was to pull the entire repo, then run docker-compose.yml, but it results in a bunch of errors
the docker-compose file in the extras folder seems to be exclusively focused on the dev environment, and I just want to have the latest release of wger running on my server. Any idea what could be the issue? I've tried following the docs but I am still a bit confused.
Originally posted by @AlexKalopsia in #340 (comment)
The text was updated successfully, but these errors were encountered: