New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

implementation of IS_RUNNING and IS_LISTENING_ON_PORT failed #8

Open

xinity opened this issue Jan 4, 2016 · 0 comments

xinity commented Jan 4, 2016

been working on implementing both (IS_RUNNING and IS_LISTENING_ON_PORT)

problem is at build time, cmd/entrypoint dockerfile instructions are not triggered, so we can't easily implement these tests.

i've tried to find an easy and clean way to trigger CMD/ENTRYPOINT instructions and then fire up tests, but failed.

a clean way is to trigger a "docker run -d" of the tested container at @DOCKER_RUN instruction in the Dockerfile_test using docker go client.

any clue appreciated :)

xinity mentioned this issue

ADD IS_RUNNING #6

Open

l0rd mentioned this issue

Implement IS_INSTALLED, OS_MATCH, FILE_CONTAINS #3

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment