-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
backend does not start #90
Comments
I commented and uncommented commands in |
It seems that this error relates to WSL, not to any particular Docker image / container. I resolved it, closing the issue. |
Problem persists:
AND
|
Hi @joehoeller, in my case it was an issue related to Windows Subsystem for Linux. It seems that WSL doesn't properly handle volumes, so I moved my project to regular Windows and it works now. Please try to make sure that |
Its like the DB on PORT 5432 (Postgres) doesnt even generate, it looks
like it doesnt exist; Trafik doesnt launch either.
…On Thu, Jan 2, 2020 at 2:36 PM M. Yusuf Sarıgöz ***@***.***> wrote:
Hi @joehoeller <https://github.com/joehoeller>, in my case it was an
issue related to Windows Subsystem for Linux. It seems that WSL doesn't
properly handle volumes, so I moved my project to regular Windows and it
works now. Please try to make sure that ./backend/app is properly mounted
as a volume inside the container.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHVQHDUIG4E4QNEJU4PFDDQ3ZF5VANCNFSM4J6BZJEQ>
.
|
Yo — I’m a pretty upfront person and support all my GitHib projects, so
with that said, here’s to keeping it real:
Why don’t you clone the repo and try running it by going thru the steps and
fix your broken repo?
This problem isn’t fixed and I am on Linux.
…On Thu, Jan 2, 2020 at 3:06 PM joe hoeller ***@***.***> wrote:
Its like the DB on PORT 5432 (Postgres) doesnt evemn generate, it looks
like it doesnt exist
On Thu, Jan 2, 2020 at 2:36 PM M. Yusuf Sarıgöz ***@***.***>
wrote:
> Hi @joehoeller <https://github.com/joehoeller>, in my case it was an
> issue related to Windows Subsystem for Linux. It seems that WSL doesn't
> properly handle volumes, so I moved my project to regular Windows and it
> works now. Please try to make sure that ./backend/app is properly
> mounted as a volume inside the container.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#90>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABHVQHDUIG4E4QNEJU4PFDDQ3ZF5VANCNFSM4J6BZJEQ>
> .
>
|
I struggled with this issue a while... tried to mount files in a seperate drive away from Windows C, tried running Docker in Windows mode, tried all the fixes offered here, none worked. What worked for me was to do the same as in this issue: I know the solution says its a cookie cutter issue, but the line endings are still wrong in the source of this repo. Should I do a PR? |
I had the same issue on windows. |
Thanks @monatis for reporting back and closing the issue 👍 Thanks @AkashV10 for the tip. If anyone else is still having problems, please create a new issue (unless you already did 😅 ) |
Hello, I will need your help, I am having the problem you had from the beginning in api send me this:
|
docker-compose up -d
starts each one of the services, butbackend
service fails with the following:docker-compose logs backend
I tried to get into the
backend
's bash to try debugging, but it also fails:docker-compose exec backend bash
ERROR: No container found for backend_1
The text was updated successfully, but these errors were encountered: