testcontainers/testcontainers-java

Improve error messaging when no docker-machine VM exists

Open

#307 opened on Mar 3, 2017

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Java (1,588 forks)batch import
client/docker-machinehelp wantedresolution/acknowledgedresolution/somedaymaybetype/feature

Repository metrics

Stars
 (7,535 stars)
PR merge metrics
 (Avg merge 2d 17h) (2 merged PRs in 30d)

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

Research direction
Inspect the DockerMachineClientProviderStrategy class and modify the error message to be more descriptive when no docker machine VM exists. Consider checking for VM existence before executing the status command.
Tech stack
java
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70