You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker-compose up -d starts each one of the services, but backend service fails with the following:
docker-compose logs backend
Attaching to iaas_backend_1
�[36mbackend_1 |�[0m Checking for script in /app/prestart.sh
�[36mbackend_1 |�[0m There is no script /app/prestart.sh
�[36mbackend_1 |�[0m INFO: Uvicorn running on http://0.0.0.0:80 (Press CTRL+C to quit)
�[36mbackend_1 |�[0m INFO: Started reloader process [1]
�[36mbackend_1 |�[0m ERROR: Error loading ASGI app. Import string ":app" must be in format "<module>:<attribute>".
�[36mbackend_1 |�[0m INFO: Stopping reloader process [1]
I tried to get into the backend's bash to try debugging, but it also fails:
I commented and uncommented commands in docker-compose.dev.command.yml so that backend should be able to run indefinitely, and now could get into that container with docker-compose exec backend bash. The problem is that /app directory is empty in the container. Something prevents it from mounting volumes on the host machine. What might be the reason for that? A permission issue?
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 ./backend/app is properly mounted as a volume inside the container.
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: #41
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?
Activity
monatis commentedon Dec 21, 2019
I commented and uncommented commands in
docker-compose.dev.command.ymlso thatbackendshould be able to run indefinitely, and now could get into that container withdocker-compose exec backend bash. The problem is that/appdirectory is empty in the container. Something prevents it from mounting volumes on the host machine. What might be the reason for that? A permission issue?monatis commentedon Dec 24, 2019
It seems that this error relates to WSL, not to any particular Docker image / container. I resolved it, closing the issue.
daddydrac commentedon Jan 2, 2020
Problem persists:
AND
monatis commentedon Jan 2, 2020
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
./backend/appis properly mounted as a volume inside the container.daddydrac commentedon Jan 2, 2020
daddydrac commentedon Jan 3, 2020
robido commentedon Feb 20, 2020
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:
#41
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?
akashvibhute commentedon Mar 6, 2020
I had the same issue on windows.
Fixed with running
find . -type f -exec dos2unix {} \;in git bash under the project root.https://stackoverflow.com/questions/7068179/convert-line-endings-for-whole-directory-tree-git
This will convert all files to LF.
tiangolo commentedon Apr 7, 2020
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 😅 )
danielbf92 commentedon Jul 1, 2020
Hello, I will need your help, I am having the problem you had from the beginning in api send me this:
ERROR: Error loading ASGI app. Import string ": app" must be in format "<module>: <attribute>".danielbf92 commentedon Jul 9, 2020
@tiangolo
✨ Add auth to Playwright and update setup (#90)