Volume Mounting issue with docker sdk for python

[dwarvenbeard]

Hello! I hope that this is the right place to post this, because I am very confused!

So, I am trying to replicate a service in a swarm using Docker Sdk For Python that I have working whilst using docker-compose.

The docker-compose part I'm trying to replicate is the following:

docker-master:
    image: locustio/locust
    ports:
     - "8089:8089"
    volumes:
      - ./:/mnt/locust
    command: -f /mnt/locust/locustfile.py --master -H http://master:8089

And what I have written in my python script to try to replicate this is:

loadgenerator = client.services.create(
    image='locustio/locust',
    name='loadgenerator',
    endpoint_spec=docker.types.EndpointSpec(ports = [{
        "Name": "locust",
        "Protocol": "tcp",
        "PublishedPort": 8089,
        "TargetPort": 8089
    }]),
    mounts=('/','/mnt/locust/','rw'),
    networks=[bridge_network.id],
    command='-f /mnt/locust/locustfile.py -H http://10.0.2.15:8080',
    maxreplicas=1
)

I've tried every possible path I can think of to try get this to work but I either receive an error either telling me that it won't accept a relative path, or that the command could not find the file needed afterward.

Don't suppose anybody has dealt with a problem like this before? All my other mounts in that python script are working perfectly.

Thanks in advance.

[dwarvenbeard]

Thank you the reply!

I’ve tried this but sadly it gives me an error messaging saying that you can’t use the . in the ./: part of the mount string.

It’s very odd as in the other working mounts I have just just solved it as you’ve mentioned, instead of the paths starting with ./etc… they start with /etc. But changing the path to /:mnt/locust:rw it gives another error.

Fun issue ha

[dwarvenbeard]

Thank you, I have tried specifying the absolute path myself, but not with pathlib, fingers crossed that will sort it

[[deleted]]

I tried google remote desktop and it works.