3 ms·
My standard way of "smoke testing" docker images is to run a verify script at the end that just checks all the expected binaries are in the path, and tries to a
by ukoki 9y ago
My standard way of "smoke testing" docker images is to run a verify script at the end that just checks all the expected binaries are in the path, and tries to access any expected environment variables while `-u` is set.
https://github.com/EngineerBetter/concourse-up/blob/master/ci/docker/Dockerfile#L49-L50 https://github.com/EngineerBetter/concourse-up/blob/master/c...
https://github.com/EngineerBetter/concourse-up/blob/master/ci/docker/verify_image.sh https://github.com/EngineerBetter/concourse-up/blob/master/c...
- dlor 9y agoMaintainer of container-structure-test here. Cool example! We started with something like this, but ran into some issues when trying to test images that don't contain a shell.
- perfmode 9y agoa benefit of specifying this declaratively is that you can change the implementation without changing syntax.