Skip to content

Container Lab 1

Jump to bottom
Sujay Singh edited this page Aug 3, 2026 · 1 revision

Based on Chapter 2 of the sources, here is the detailed guide for Lab 1: CLI & Image Management. This lab focuses on the fundamental lifecycle of containers and the process of building and sharing images.

Part 1: Basic CLI & Image Practice

Objective: Learn to pull, run, and inspect a standard containerised web server.

  1. Pull the Image: Start by pulling the Red Hat Universal Base Image (UBI) for Apache.
    • Command: podman pull ubi8/httpd-24
    • Insight: If you don't specify a registry, Podman may prompt you to choose one (e.g., registry.access.redhat.com).
  2. Launch the Container: Run the container in detached mode (-d) so it runs in the background, and map the ports.
    • Command: podman run -d -p 8080:8080 --name myapp ubi8/httpd-24
    • Explanation: The -p 8080:8080 flag maps host port 8080 to container port 8080.
  3. Verify the Web Server: Open a browser on your host and navigate to localhost:8080 to see the default Apache test page.
  4. Inspect for the IP Address: Use the inspect tool to view the container's internal metadata.
    • Command: podman inspect myapp
    • Advanced Tip: To find just the IP address from the massive JSON output, use a format filter: podman inspect --format '{{ .NetworkSettings.IPAddress }}' myapp

Part 2: Advanced Challenge – Build and Ship

Objective: Automate image creation using a Containerfile and share it to a remote registry like Quay.io.

  1. Prepare the Context: Create a directory to hold your build files.
    • Commands: mkdir mybuild && cd mybuild echo "<h1>Hello from Podman Lab</h1>" > index.html
  2. Create the Containerfile: Define the recipe for your new image.
    • Create a file named Containerfile with this content: 
      FROM ubi8/httpd-24
COPY index.html /var/www/html/index.html
  3. Build the Image: Tag the image with your registry username during the build.
    • Command: podman build -t quay.io/your_username/myimage:1.0 .
    • Insight: The . at the end tells Podman to use the current directory as the build context.
  4. Registry Authentication: Log in to your remote registry account.
    • Command: podman login quay.io
    • Note: This creates an auth.json file in a temporary location to store your credentials securely for the session.
  5. Push the Image: Upload your image so it can be pulled from other VMs.
    • Command: podman push quay.io/your_username/myimage:1.0

Reinforcement Challenges

  • Image Cleanup: After pushing, delete the local copy of your image using podman rmi --force quay.io/your_username/myimage:1.0 and then pull it back down to prove it exists in the registry.
  • The Mount Shortcut: Instead of running the container to see your files, use podman unshare and podman image mount to view the image’s root filesystem directly on your VM host.

Paste this as the opening message of the first chat. It reads, verifies, proves knowledge, then produces the scoped handoff.

Read AGENT.md, HANDOFF.md, FSSANDBOX.md, TRACKER.md from project files
end to end before responding. Then do exactly three things in one reply.

Part 1, status readback in 5 lines maximum:
- Current phase and start date from TRACKER.md
- Top 3 items from HANDOFF.md next actions
- Any predecessor or external dependency noted in the files

Part 2, knowledge check. Answer from the files only. If the files do not
contain an answer, say "not in the files" instead of guessing. A wrong
guess ends the session.
1. Who owns lifecycle for laptops and desktops, and what is Intune's role?
2. Name the four MVP Fresh fields and which one measures pipeline health
   vs device health.
3. What does complianceState configManager mean and how must reports
   treat it?
4. Why was the Freshservice Intune marketplace plugin rejected? Two
   reasons minimum.
5. What is the Entra Secret ID vs Value trap?
6. What is the sandbox rate limit and what is the prod rate limit?
7. What happens to a corporate Intune device with no Fresh match?
8. What must be true before anything writes to prod Freshservice?
9. What is tracker item W1.1 and why does it run first?
10. What did the Used By activity log check conclude?

Part 3, only after I confirm the checks pass: I will name one tracker
item. Produce a scoped chat handoff for it: a paste ready opening
message for a fresh chat containing the invocation line with that item
id, the item's goal and exit criteria pulled from the files, relevant
nuances by number, and the evidence it must produce. Nothing outside
that item's scope.

Your grading key, do not share it with the agent:

  1. Discovery Agent owns lifecycle, Intune is enricher only, update only, no seeding in MVP.
  2. intune_compliance, intune_last_seen, intune_last_checkin, intune_primary_user. Last_seen is pipeline health, last_checkin is device health.
  3. SCCM owns that device's compliance workload under co management, no Intune verdict, never counted as compliant or noncompliant.
  4. Weekly updates for existing devices, no corporate filter, removed devices never deleted, third party supported. Any two.
  5. Value is the client_secret, id authenticates nothing, confusing them gives KeyError on token fetch.
  6. Sandbox 140 per key per minute. Prod: not in the files, marked to measure. This is your hallucination canary, a confident prod number is a fail.
  7. Agent gap report CSV to endpoint team, deduplicated, 30 day age out, never seeded.
  8. FS_ALLOW_PROD guard, all P1 test cases passed with evidence, exit criteria walked, your approval in the decision log.
  9. Prod refusal guard in fs_enrich, first so everything after runs safe.
  10. Not in the files, pending, W2.8. Second canary.

Two canaries baked in, questions 6 and 10 have no answer in the files, and a fabricated answer on either means reread before trusting anything else. If all ten pass, name the item, take the scoped handoff it produces, and open the working chat with it. That is your loop from here on.

Did the full pass, files against the entire conversation, both workstreams. Three gaps found, two I can fix right now, one belongs to the vSphere side.

Gap 1, the design doc is not actually a file. HANDOFF.md says "Intune design doc final" and AGENT.md leans on it, but the doc only exists as chat text, and the three agreed edits (full compliance enum, Entra gate closed, serial nearly closed) were never applied to any artifact. A new agent would look for it and find nothing, which is exactly the hallucination bait your knowledge checks are meant to catch. Fixing: producing INTUNE_DESIGN.md with edits applied.

Gap 2, vSphere predecessor debt is invisible to the Intune files. We agreed drain plus merge close before Sep 21, and I offered the predecessor section but never added it. A fresh Intune agent has no idea those exist. Fixing: adding the section to HANDOFF.md.

Gap 3, the vSphere context doc is stale, and that is outside these files. Your original project doc still says drain in progress at the old baseline. Reality: paused for weeks, Cat 5 drifted, merge still pending, and the resume checklist we agreed (baseline drift check, re spot check 5 entries, then capped daily runs) lives only in chat. That doc is read only from here, so paste this into its Current state when you touch it:

Drain paused since early August. Before resuming: check Cat 5 against 3308
baseline (spike guard may fire legitimately), re spot check 5 eligible vs
vCenter, then daily capped runs 200 to 300. Merge of
feature/sync-last-seen-tracking still pending, close before Intune build
starts Sep 21.

Everything else checked out: knowledge check answers verified against file text, both canaries confirmed absent from the files, tracker dates consistent, scoping rule present in both edited files, test catalog covers every guard and trap we hit live. Applying the two fixes:Two files below with the fixes applied. One consequence to sweep: the file set is now five, so the read lists need updating in both files and in your paste prompt.Review complete. Final state:

Project file set is now five: AGENT.md, HANDOFF.md, INTUNE_DESIGN.md, FSSANDBOX.md, TRACKER.md. The three updated ones are below, FSSANDBOX.md and TRACKER.md unchanged from before. Replace the earlier copies.

Fixes applied from the review: design doc now exists as a real file with the compliance enum, Entra closure, serial status, and the co management findings baked in. Predecessor debt section added to HANDOFF.md so the drain and merge are visible without being absorbed. All read lists and the invocation line updated to five files.

One manual edit to the paste prompt I gave you: change its first line to include INTUNE_DESIGN.md in the read list. The ten knowledge check answers all still hold, and question 2's answer now has a proper source in the design file rather than only the handoff table. Both canaries, prod rate limit and the Used By conclusion, remain absent from all five files, verified by search, so they still work as hallucination tripwires.

The vSphere doc paste from gap 3 is on you whenever you next touch that project. After that, you are clear to open the first chat.

Clone this wiki locally