nginx does not start... about django-on-docker

[apocalypse2012]

Found it! In the Nginx section of your tutorial: https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/#nginx
...there is a test link near the end of the section. This test link is to prove app operation through the nginx routing. At the point at which this link is presented, /admin is still the only valid url.
Here is the link as presented in the tutorial section...
http://localhost:1337/
If I were more experienced I would have likely caught it without even thinking about it. More over, I might have just not clicked the link, finished the tutorial without checking, and by the time I got to it, the link would have been good. As it is, it was just enough to send me flailing.

[mjhea0]

Often, when you get a page not found like that, the underlying issue is with the application that you're trying to serve up not Nginx. I would focus time on figuring out if there is something wrong with the Django application, in other words. Have you looked at the Docker logs? If you expose the Django application itself via ports--

ports:
   - 8000:8000

--can you view the app from port 8000?

[apocalypse2012]

Yes, I can get to the application on 8000. There is nothing in the log after the section for the ‘web’ container. The container for nginx does not appear in the docket list or the logs. The logs do not show any errors or warnings for ‘web’. It’s as if the nginx container builds but just does not start. The code for the project is a literal line by line read-through of the tutorial. No customization. I have read in other pages that their are problems starting nginx in docker unless you run it in the foreground. They have startup scripts that do just that. But your example does not. Just a very simple docker file and apparently the default startup sequence with your custom configuration. What could I be missing?

…

Sent from my iPhone

On Dec 29, 2021, at 9:51 AM, Michael Herman ***@***.***> wrote:  Often, when you get a page not found like that, the underlying issue is with the application that you're trying to serve up not Nginx. I would focus time on figuring out if there is something wrong with the Django application, in other words. Have you looked at the Docker logs? If you expose the Django application itself via ports-- ports: - 8000:8000 --can you view the app from port 8000? — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.

[mjhea0]

I'm not sure. I just tested it out and it works on my machine. (I'm on a mac).

test.mp4

Test it out in the same way. If it works, then you may have missed something in the tutorial. If it doesn't, then it may be an environment specific issue. What kind of machine are you on? I've updated this tutorial 3 or 4 times in the past few years, so it's been tested a number of times.

[apocalypse2012]

I'm also on a Mac. This is the second time I've done the tutorial and hit the same problem in the same place. Are you sure there is not an unlisted dependency? Cheers, Raymond Stewartportfolio) linkLinkedIn) linkresume) linkcel) 678-362-4994skype) rts324😂🤣😵☠️🧟‍♂️ On Thursday, December 30, 2021, 10:35:23 AM EST, Michael Herman ***@***.***> wrote: I'm not sure. I just tested it out and it works on my machine. (I'm on a mac). https://user-images.githubusercontent.com/2018167/147765780-c10ca20f-a5db-4d80-9759-8e4ab86bd4c5.mp4 Test it out in the same way. If it works, then you may have missed something in the tutorial. If it doesn't, then it may be an environment specific issue. What kind of machine are you on? I've updated this tutorial 3 or 4 times in the past few years, so it's been tested a number of times. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[mjhea0]

Yes

[apocalypse2012]

OK, trying this out again. The issue is not exactly as I reported before. Nginx does appear to be running. Its just giving me 404s. For some reason its not getting through to the app. Likewise, I cannot bring up the app by accessing port 8000. Not sure if this is for the same reason or if because port 8000 on the web app is not built with the expose flag instead of the ports flag and now is only supposed to be visible from other Dockers. Either way, the Nginx instance does not appear to be routing to it.
My only apparent variance from the source code in this project is that I have not yet added static files. It is otherwise the same as best as I can tell. Don't know why Nginx does not want to route to the app.

[apocalypse2012]

I'm sorry. For some reason, my iPad was not showing me your test.mp4 video, so I did not see the instructions you left. I reproduced your test case from git download and it works fine. I don't know what I missed or skipped in the following the tutorial. Doing a file by file diff to try to track it down.
Will follow up...