Docker, think of it as a clever toolbox for developers, allowing them to wrap up applications along with all their necessary bits and pieces in virtual packages called containers. These containers are like travel cases for apps, ensuring that no matter where you set up camp, everything you need is right there with you. It's like having your own portable workspace that you can carry from your backyard to the far corners of the world, and your work environment stays just the way you like it.
- Dockerfile
- .dockerignore
- index.html
-
nginx as the proxy server and base image for our container FROM nginx:1.10.1-alpine
-alpine is a super small Linux distribution Other base image options like Ubuntu could have been used, but nginx is faster and I needed to run a static page so nginx was chosen.
-
The implementation was a simple HTML file with 2 images and the command COPY src/html /usr/share/nginx/html was used to copy the files
-
docker build . After that, a name-less docker image would be created which can be accessed by using it's ID
-
To give a name to the docker image docker build -t . For eg. docker build -t first-file .
-
To view running containers, use the following command. docker ps
-
The docker images command can be used to display the images. docker images
Which should return something like this.....
-
$ docker run -it --rm -d -p 8080:80 --name web nginx With the above command, you started running the container as a daemon (-d) and published port 8080 on the host network. You also named the container web using the --name option.
-
docker start - Starts the container
-
docker stop - Stops the container (When you want to start or stop a specific container, use it's name after start/stop)