$
Learn Linux handbook
en
XP:0

Chapter 17 of 17

Deliver and troubleshoot changes

Combine version control, containers, and operational checks without confusing them with isolation guarantees.

The mental model.

Git separates the working tree, staging area, and commit history. git diff shows unstaged changes; git diff --staged shows what will enter a commit. Review both before committing. A commit is local until pushed, and version control is not a substitute for all backups.

A container is a process isolated through kernel features such as namespaces and cgroups. It shares the host kernel, unlike a VM with its own guest kernel. An image is the template; a container is an instance with runtime state.

Inspect container state, logs, published ports, and mounted volumes separately. Data in a writable container layer can disappear when the container is replaced. Use appropriate persistent storage and test recovery.

For each change, record the intended outcome, the smallest modification, verification evidence, and rollback steps. Start with observation, form one hypothesis, test it, then change one variable at a time. Avoid restarting everything before collecting logs.

Read it. Predict it. Try it.

Before running these commands, predict what each line will change or print. Launch a quest below to open the simulated terminal.

git status
git diff
git log
docker ps
docker logs web

The simulator provides practice fixtures for Git and containers. Use the operations capstone to apply the same investigation sequence to real processes and saved evidence.

Check your understanding

Explain the why.

What does a Linux container share with its host?

Put it into practice.

Complete the exercises, then try the Boss Challenge without hints. Each quest checks its own objectives. You can revisit this chapter at any time.

Prefer to read first?

Make the learning stick.

Close the explanation and describe the main idea in your own words. Change a filename or input and predict the outcome. Tomorrow, repeat a quest without hints. Then apply it in a disposable real Linux environment.

Open the real-system labs →