amazon-archives
Multiple versions of pip/python installed in monolith Dockerfile.draft
I was following along with this tutorial an AWS loft, and when following the instructions, discovered that pip and bin/pip exhibited different behaviour.
With all the capabilities of Docker, why are we using a local installation in root's home directory instead of the system installation? Likely the answer is The tutorial was written for a particular version of these softwares. But then the obvious solution is This is Docker, just drop the root filesystem and create a new one. Most users will assume that they should use pip from the $PATH.
Just curious, did you get the container to run? After typing docker run, goes back to the shell prompt, nothing listening on port 5000. I saw a few other folks with this issue.
I was able to get it running. I did have that exact issue, but after duplicating what the instructor had in her Dockerfile, I was able to proceed. Unfortunately I don't remember what the solution was.