- Python 3.5
$ pyvenv testenv
$ cd testenv
$ git clone ssh://[email protected]/ostc/docker-compliance.git
$ source bin/activate
$ cd docker-compliance
$ pip install -r requirements.txt
$ ./tern -h
$ cd testenv
$ source bin/activate
$ git clone ssh://[email protected]/ostc/docker-compliance.git
$ cd docker-compliance
$ export PYTHONPATH=`pwd`
$ python tests/<test file>.py
- Knowledge base: Each layer hash should come with a list of known packages that are installed in that layer
- Allow for exceptions or additions for the command library
- In the reporting do not ignore packages that may be installed in the docker image - see bug 4
- Harden for testing within VMware's docker community
- Script assumes user is not in the docker group
- When a command fails within a container that package should be moved over to 'unrecognized'
- For reporting purposes - parse ENV
- Report should have 3 sections: confirmed, unconfirmed, unrecognized
- docker-command should raise exceptions that can be caught in demo for exiting
- Docker API assumes user is in docker group and hence can run docker commands without sudo
- Docker has no ability to step through docker history