testcontainers / testcontainers/testcontainers-java
Improve error messaging when no docker-machine VM exists
Open
Nobody has claimed this yet.
client/docker-machine
help wanted
resolution/acknowledged
resolution/somedaymaybe
type/feature
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
e.g. in the case where the docker-machine tool is found but there's no VM.
At present the logged error is quite unhelpful:
o.t.d.DockerClientProviderStrategy : DockerMachineClientProviderStrategy: failed with exception InvalidConfigurationException (Exception when executing docker-machine status default)
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 by locating DockerMachineClientProviderStrategy, the entry point named in the logged error, and reproduce the case where docker-machine exists without a default VM. Done means the resulting error clearly explains that no VM is available instead of reporting only the generic status-execution exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- devops, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100