Challenge - Build and run

Build an image and run the container on a specific port.

Challenge: build and run

Building an image, versioning it and running it with the right options is a series of commands. In this challenge you'll do a version-tagged build, inspect the image and start it in a production-like way:

docker build --pull -t api:1.0.0 -t api:latest .
docker history api:1.0.0
docker run -d --name api --restart unless-stopped -p 127.0.0.1:3000:3000 \
  --env-file api.env --memory 256m api:1.0.0
docker logs -f api

Exercise Build and inspect

Write two commands: build from the current folder updating the base image, tagged both api:1.0.0 and api:latest; then show the layer history of api:1.0.0.

Show example solution

docker build --pull -t api:1.0.0 -t api:latest .
docker history api:1.0.0

Exercise Run like production

Start a container named api from api:1.0.0 with one command: in the background; restarting unless stopped by hand; port 3000 published only on 127.0.0.1; settings from api.env; memory limited to 256m.

Test yourself

In this run, can the API be reached from another computer on the same network?
- Only if --memory is removed
- No, the port is bound only to 127.0.0.1
- Yes, through port 3000
- Only after a restart
Show answer

No, the port is bound only to 127.0.0.1 — To expose it, a reverse proxy is usually put in front.

Limit the container's memory.

docker run -d ____ 256m api:1.0.0

Show answer

docker run -d --memory 256m api:1.0.0

Match.

--pull

Fresh base image
--restart unless-stopped

Resilience
--env-file

Settings
127.0.0.1:3000:3000

Local access only

Next lesson: Challenge - Volume

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies