m-bus | Modbus TCP and RTU stack for embedded devices | TCP library

There is no package named apt-clone in the public PyPI repository, so pip3 obviously cannot find it.

If you actually have a Python package named like this, where did it come from?

• If you created a package with this name locally, you need to install it too in your Docker image somehow.

• If you are inside an organization, maybe you have a local PyPI with different packages than the public one, and then you need to configure pip3 to use it (try pip3 -i http://your.local.pypi/simple -r requirements.txt where obviously the URL needs to be something else, but we can't guess what).

If pip3 freeze says you have this package, it must have come from somewhere, but we don't know where. You have to figure that out, or supply more details to help us help you.

There is a Debian package named apt-clone but that obviously isn't something pip can install. Did you actually mean apt-get install -y apt-clone==0.2.1? (I can only find version 0.4.1 in Debian Buster, though.)

... @atline's answer explains what happened (you should probably accept that) but the simple fix is to manually populate requirements.txt with your actual requirements. pip3 freeze is a nice shorthand for that if you are in a virtual environment, but it's not a proper replacement for a manually curated requirements.txt or setup.py (or its modern replacements, currently moving from setup.cfg to pyproject.toml). If flask is the only package your app needs, simply put pip3 install flask and don't create a requirements.txt.

It's been three weeks with no responses, but I just wanted to update with what I've found. In all cases where I've left "docker-compose up" running it eventually started.

At times it took 30 minutes, but it started every time.

You don't keep them inside the image. Instead, you pass the contents of the envfile in to the docker run command from the outside.

According to the documentation for mysqlclient you'll need to have default-libmysqlclient-dev and a compiler installed on the system, so if you install it before running pip install it should work (I tested it, but of course without your app code)

While debugging I figured out that I was not exposing the port at the dockerfile and therefore it was not able to deploy the container correctly. I also added python as an entry point and the script name as the cmd.

Finally after some investigation also realized that the container inherits all role permissions that the host has so there is not need to do any additional task

My docker file end up looking like this:

As the error tells us, we have to simply install git, so that pip can clone the repo and run the setup file. We can install git with

With the help of https://blog.jetbrains.com/pycharm/2017/03/docker-compose-getting-flask-up-and-running/ this is now working.

Dockerfile:

The traditional way is via environment variable

I recommend you to use docker-compose for running and using your image and set any environment variables you want. A sample of the docker-compose file could be like this: