Feature Request: `driver_opt` parameter of `Networks.connect` in `Containers.create`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Currently,
the Networks.connect method takes the driver_opt parameter in order to pass to the driver some custom values: https://docker-py.readthedocs.io/en/stable/networks.html#docker.models.networks.Network.connect.
I have a custom Network Plugin which uses such parameters to generate the MAC Address.
However, it is not possible to specify any custom value while attaching the first Docker network using Containers.create or Containers.run.
Is it possible to expose this parameter in such methods?
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The request concerns Containers.create and Containers.run, alongside Networks.connect; start by tracing how the first network attachment is assembled and how driver_opt is forwarded there. Done means both container entry points can accept and pass the custom network option consistently; check the existing network and container tests for coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100