goss VS container-structure-test

Certain checks may be possible with goss and the kgoss wrapper: https://github.com/goss-org/goss/tree/master/extras/kgoss

Docker would work. I suggest also integrating infrastructure tests to validate your install script behaved as expected. For example, you could use goss.

I've used https://github.com/goss-org/goss in the past and enjoyed it

To answer my own question... https://github.com/goss-org/goss looks like it might do the job - at least for Linux. Windows support is alpha - and there isn't a wealth of CIS benchmarks. Might be a good project to contribute to

Adding an extra layer of security on the container image to verify if it is working as expected and has all required files with correct permissions. We can use dgoss to do validation tests of container images.

Bit of a strange one here - Goss. This is a testing tool that we use on all of our servers to validate they are working as expected. Think of it as a sanity check after changes. We have a set of tests setup that validate that the server is working as expected and we run it automatically after any change.

check out https://github.com/aelsabbahy/goss

Use GOSS, a YML-based open-source tool that can assert the test results (i.e., verifying if the SSH port 22 is closed or not).

Testing your container : container-structure-test https://github.com/GoogleContainerTools/container-structure-test

There is a way! Google's container structure test is the answer. container-structure-test.

Container Structure Tests (CST) is a container-testing tool developed by Google and open-sourced with the Apache 2.0 license. CST comes with a predefined set of tests for looking at what’s actually inside a container image.

The best tool I can raccomand to write a unit test for a Docker is the Container Structure Test framework. This framework, developed by Google, makes super easy to test the structure of your container image.