Pass Arguments To Python Argparse Within Docker Container

I am embarking on my first attempt at utilizing a docker container. I have a python script that calls a couple API's and parses a file. The script took parameters for the URL of

Solution 1:

The way you do it depends on how your using docker. If you want to run your script in an already running container, you can use exec:

docker exec <yourContainerName> python <yourScript><args>

Alternatively, if you have a docker image where your script is the ENTRYPOINT, any arguments you pass to the docker run command will be added to the entrypoint.

So, if your docker file looks like this:

FROM yourbase
....
ENTRYPOINT <yourScript>

Then you can just run the script by running the container itself:

docker run --rm <yourImageName><args>

Based on your comment below, it looks like you want this option. You should change your dockerfile to specify

ENTRYPOINT ["python","./script.py"]

(instead of using CMD) and then you can run via:

docker run --rm <yourImageName>  -a API_KEY - f FILENAME -o ORG_ID

Solution 2:

So let's assume your command is below

python app.py "URL""APIKEY""filepath"

So you will put your Dockerfile in below fashion

FROM python:3.6
WORKDIR /app
COPY app.py .
ENTRYPOINT ["python", "app.py"]

Then the person running the docker container would do it like below

docker run -v /home/tarun/project/filetoparse.yaml:/config.yaml <yourimagename> "URL""APIKEY" /config.yaml

If you want to give more flexibility you an can even use environment variables

docker run -v /home/tarun/project/filetoparse.yaml:/config.yaml -e APIKEY="XYZ" <dockerimage> "URL" /config.yaml

And then in your script you can read it using os.environ['APIKEY']

Solution 3:

Inside Dockerfile, i use the CMD command like this:

FROM python:3COPY ./app /app
WORKDIR /app
RUN pip install --upgrade pip
RUN pip install --no-cache-dir -r req.pip
CMD ["python","start.py","(api-url) ","(api-key)","(file-path)"]

Note Per each args/params, separate with coma

If you are using flags, you will need to split

CMD ["python","start.py","-u","(api-url) ","-k","(api-key)","-f","(file-path)"]

Solution 4:

This answer is kind of late but for any future readers, i would like to make it more towards the question asked i.e. with respect to argparse.

The basic idea like @Chris pointed out is it. One way to achieve the solution is to pass arguments to the image in docker run command itself. These arguments would then be passed to your ENTRYPOINT, therefore passing to the python script.

The files would look something like this typically..

file.py

import argparse
parser = argparse.ArgumentParser(description='Process some integers.')
parser.add_argument('pos', type=str, help='Example Positional Argument') # will be accesible under args.POS
parser.add_argument('--opt', type=str , help='Example Optional Argument') # will be accesible with args.OPT

args = parser.parse_args()

# do something with pos and OPT

Without docker, You would run this file (assuming it is in the pwd) as python file.py --opt opt_val pos_val

Dockerfile

FROM python:<your_tag>
COPY ./file.py ./ # Assuming your Dockerfile and file.py are in the same directory# some custom build steps

ENTRYPOINT ["python","./file.py"]

Docker build and run commands

You build with this : docker build --tag example:0.0.1 <dir>

The below shows multiline(for better readability) run commands,

Docker run

docker run --rm \--name example.container \
   example:0.0.1 \
   --opt=opt_val \
   POS=pos_value

Docker run (powershell)

docker run --rm `--name example.container `
   example:0.0.1 `
   --opt=opt_val `
   POS=pos_value

So here are some points to remember:

• Argparse has support for adding positional and optional arguments and should be passed accordingly to the image in the docker run command.
• The solution pointed out above works but is not as flexible as id generally like it to be. Better to use Environment variables and access inside the script with os.environ().
• With this solution you dont "hard-code" anything to the Dockerfile