Docker commands reference for containerized developer toolkit environment

Docker commands to perform common tasks in your containerized developer toolkit environment.

Table 1. Docker command reference
Command	Description
`docker images`	See all your images. You can see at least four images corresponding to application server, Db2 server, MQ server, and OMS runtime.
`docker ps`	See all running containers. You can see at least four active containers corresponding to application server, Db2 server, MQ server, and OMS runtime.
`docker logs -f --tail 100 <container_name>`	See the running logs of the given container starting with the last 100 lines.
`docker exec -it <container_name> bash`	You must run the commands inside a container as a `sudo` user. Note: Be careful while you run commands inside a container. Running unverified commands can make your container unusable and you might have to do fresh setup again. Enter an active container as a default container user. Note: The default user in the runtime container of the developer toolkit is changed to a non-root user. The username if the default non-root user is `omsuser` with user ID as 1000 and group ID as 1000.
`docker start <container_name>`	It is recommended to use the commands in Docker Compose commands reference to start, stop, or restart one or all services rather than directly using the Docker commands.
`sudo systemctl start docker`	Start the Docker daemon.
`sudo systemctl enable docker`	Permanently enable Docker daemon.
`sudo service docker status`	Check whether Docker daemon is running.