Accessing remote server via DOCKER_HOST eats all memory
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Accessing remote server via SSH and running command eats all the memory.
Using the same command in server itself has no problem.
For instance,
I have a docker compose file in my local, if I run the command below, it eats all the memory and server shuts down.
DOCKER_HOST=ssh://blabla docker compose up
but, if I copy the same compose file to server and run the docker compose up command only uses ~50MB memory.
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
Reproduce the issue with DOCKER_HOST=ssh://blabla docker compose up and compare its memory usage with running the same compose file directly on the server. Trace the Docker CLI's SSH remote execution path to identify why the remote command consumes all available memory; done when the remote compose command completes without exhausting the server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100