max-mapper / max-mapper/docker-stream
boot2docker issues
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 68
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
some annoying things about boot2docker that users shouldn't have to know about to use docker-stream
- you have to run
boot2docker upand then run docker withDOCKER_URLenv variable set to theboot2docker ip(this issue is already mostly handled bydocker-stream) - if you want to expose a port from inside the container you have to do this arcane command first (while
boot2dockeris down):VBoxManage modifyvm "boot2docker-vm" --natpf1 "guestnginx,tcp,,4000,,4000" - you can't currently do
-vto mount volumes from local host into the container when using the docker remote protocol (which is what docker uses when usingDOCKER_URL). - boot2docker seems to drop the internet connection which you switch between wifis / your computer goes to sleep
Contributor guide
No contributing guide indexed for this repository
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 source files, tests, or entry points are named. Start by examining how docker-stream handles boot2docker and the DOCKER_URL environment variable, then investigate the listed port forwarding, volume mounting, and network reconnection cases. Done means users no longer need these boot2docker-specific workarounds when using docker-stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100