driver_config: Only valid for the volume type?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Documentation states that
Mount.driver_config(DriverConfig) – Volume driver configuration. Only valid for the volume type.
Is there any reason for that? Why overlay wouldn't be supported (volume-opt equivalent)?
I don't see reference to this limitation in the codebase, where is it?
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
Start with the Mount API documentation and the Mount.driver_config reference, then search the codebase for driver_config and the volume-opt handling mentioned in the issue. Determine whether the volume-only limitation is enforced or only documented; done means a decided explanation and corresponding documentation or implementation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100