Three hosts, one tag, three images
Three hosts pull payments-gw:latest and each runs something different. Compare digests with the signed release list and the registry push log to find the image nobody released.
What you’re looking at
Three hosts pull payments-gw:latest and each runs something different. Compare digests with the signed release list and the registry push log to find the image nobody released.
Your goal: Find the image that nobody released hiding behind the latest tag.
- Briefing
- the story: what happened and what evidence you were handed.
- Terminal
- the dark box. It is a pretend Linux shell that runs in your browser. Type a command and press Enter. Nothing you type touches a real system.
- Walkthrough
- the numbered path. Each step says what to type and what you should see. Hints open one at a time.
- Answer boxes
- under each question step. Type what you found and press Check.
Words you will meet
- IP
- Internet Protocol address, the number that identifies a machine on a network
Start with step 1 in the walkthrough. Every step says what to do and what you should see. The whole thing takes about 2 min to talk through.
Briefing
payments-gw runs on three hosts, all deployed from the same compose file with image: registry.example/payments-gw:latest. A customer reported odd behaviour on one host only.
A tag is a movable pointer; a digest (sha256:…) names exact bytes. Release engineering signs and records the digest of every release.
deploy-01 · Container audit
Type help for the command list and objectives for your tasks. Everything runs in this browser.
Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.
The whole walkthrough
Every step in order, written to be read aloud: 299 words, about 2 min. It gives away every answer, so try the steps first.