-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
[BUG] Portainer can't find manage.py #987
Comments
"./backend" should be mapped to "/app" in the container. It was for backward compatibility. |
I have the same problem. Like a work arodun I had to download the github manually and run with portainer. |
I tried this but then see these warning...
and this error...
|
@spusuf, try using the solution I detailed in my comment in another issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the image or git is pulled then started using
docker compose up -d
the server starts as expected, but using Portainer to launch results in obico-web logs showing:And obico-tasks logs show:
However changing the backend volume in
docker-compose.yml
from- ./backend:/app
to:- ./backend:/backend
worksAdding the line
-./backend:/app
does not work.Is there a reason why the frontend volume points to the frontend directory, but backend points to a directory that doesn't exist in the root folder? Again this is only an issue in Portainer but the fix works for docker compose.
Just want to get a little bit of insight as to why it's set up this way and what I need to fix in a PR to get working on both platforms.
The text was updated successfully, but these errors were encountered: