Creating a Systemd Compatible Debian Container

Your development team continues the development of a new Web-based API. They have thus far been working on full virtual systems running Apache. However, they are ready to start breaking out their non-production environments (QA, User Acceptance, Load Testing, etc). Since these non-production environments will not be in use constantly, there is no need to dedicate full instances to them.

As a result, you have been provided credentials and login information to a CentOS 7 system intended to be shared amongst a variety of non-production environments that will be ephemeral in nature. However, it is important for them to otherwise match the production implementation.

You have been asked to configure a Debian container within the CentOS 7 host you are working on. This container will be the first non-production environment on this host and the developers will be using this to build out the Test environment, keeping it separate from the underlying host.

You will need to install the necessary packages and filesystem structure to the appropriate location to create a container called 'test'. Once you are able to launch the container using the appropriate 'systemd' command, you will need to connect to it and provision two users (see below - do not forget to rename the PAM module within the container to allow users to login to it directly).

Finally, set the container with systemd so that it runs as a service and will restart anytime the system itself is restarted. Once you verify it is running, you can turn it over to the development team for use.

USERS TO ADD
Jon Riker - Username: jriker
Dee Troy - Username: dtroy

Note: To permanently disable selinux: vi /etc/sysconfig/selinux and set the following: SELINUX=disable and restart.