A guide on how to use docker-py with SSH for volumes.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
I have been using the provided features for Docker using SSH transport and it works great for starting up containers and API calls. Currently I am experiencing issues getting some containers working with volume mapping over SSH.
Is there any preferred way to achieve a volume mapping between the remote docker host and the machine docker-py is running on ? My issue in particular is it seems that the filesystems directories are created but the contents of the volume isin't transferred over.
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
No file, test, or documentation entry point is named. Start by investigating Docker SSH transport and volume-mapping behavior, especially whether contents should transfer between the local and remote hosts. Done means a guide explains the preferred setup and the expected handling of remote volume contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100