Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · English

Docker Socket Risk (EN)

This detail document describes example 29-docker-socket-risk. Focus: Socket-Mounts, CI-Risiken und Schutzmaßnahmen.

Content language · EnglishSize · 43.1 KBexamples/29-docker-socket-risk/docs/en/README.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 7 chapters read
Other language versionGerman ↗Greek ↗

Docker Socket Risk (EN)

This detail document describes example 29-docker-socket-risk. Focus: Socket-Mounts, CI-Risiken und Schutzmaßnahmen.

Learning Goals

  • Name Docker resources before execution.
  • Read artifacts and mark risks.
  • Separate local validation from real execution.
  • Store evidence in a traceable way.
  • Document cleanup and boundaries.
01 / 07

Flow

  1. Open the files in the example directory.
  2. Read commands.sh before executing commands.
  3. Validate Dockerfile, compose.yaml, JSON files and shell scripts with ./run.sh.
  4. Decide explicitly whether you want to run real Docker commands.
  5. Remove lab resources after execution.
02 / 07

Expected Observations

  • Observation 01: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 02: Check Build context and record which Docker command makes the observation reliable.
  • Observation 03: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 04: Check Network and record which Docker command makes the observation reliable.
  • Observation 05: Check Volume and record which Docker command makes the observation reliable.
  • Observation 06: Check Logs and record which Docker command makes the observation reliable.
  • Observation 07: Check Security and record which Docker command makes the observation reliable.
  • Observation 08: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 09: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 10: Check Build context and record which Docker command makes the observation reliable.
  • Observation 11: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 12: Check Network and record which Docker command makes the observation reliable.
  • Observation 13: Check Volume and record which Docker command makes the observation reliable.
  • Observation 14: Check Logs and record which Docker command makes the observation reliable.
  • Observation 15: Check Security and record which Docker command makes the observation reliable.
  • Observation 16: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 17: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 18: Check Build context and record which Docker command makes the observation reliable.
  • Observation 19: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 20: Check Network and record which Docker command makes the observation reliable.
  • Observation 21: Check Volume and record which Docker command makes the observation reliable.
  • Observation 22: Check Logs and record which Docker command makes the observation reliable.
  • Observation 23: Check Security and record which Docker command makes the observation reliable.
  • Observation 24: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 25: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 26: Check Build context and record which Docker command makes the observation reliable.
  • Observation 27: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 28: Check Network and record which Docker command makes the observation reliable.
  • Observation 29: Check Volume and record which Docker command makes the observation reliable.
  • Observation 30: Check Logs and record which Docker command makes the observation reliable.
  • Observation 31: Check Security and record which Docker command makes the observation reliable.
  • Observation 32: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 33: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 34: Check Build context and record which Docker command makes the observation reliable.
  • Observation 35: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 36: Check Network and record which Docker command makes the observation reliable.
  • Observation 37: Check Volume and record which Docker command makes the observation reliable.
  • Observation 38: Check Logs and record which Docker command makes the observation reliable.
  • Observation 39: Check Security and record which Docker command makes the observation reliable.
  • Observation 40: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 41: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 42: Check Build context and record which Docker command makes the observation reliable.
  • Observation 43: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 44: Check Network and record which Docker command makes the observation reliable.
  • Observation 45: Check Volume and record which Docker command makes the observation reliable.
  • Observation 46: Check Logs and record which Docker command makes the observation reliable.
  • Observation 47: Check Security and record which Docker command makes the observation reliable.
  • Observation 48: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 49: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
  • Observation 50: Check Build context and record which Docker command makes the observation reliable.
  • Observation 51: Check Container lifecycle and record which Docker command makes the observation reliable.
  • Observation 52: Check Network and record which Docker command makes the observation reliable.
  • Observation 53: Check Volume and record which Docker command makes the observation reliable.
  • Observation 54: Check Logs and record which Docker command makes the observation reliable.
  • Observation 55: Check Security and record which Docker command makes the observation reliable.
  • Observation 56: Check Cleanup and record which Docker command makes the observation reliable.
  • Observation 57: Check Socket-Mounts, CI-Risiken und Schutzmaßnahmen and record which Docker command makes the observation reliable.
03 / 07

Review Checklist for Example Docker Socket Risk

  • 01. document context and desired state: record the affected Docker resource, the command that proves state and the rollback path.
  • 02. explain the command before running it: record the affected Docker resource, the command that proves state and the rollback path.
  • 03. prove current state with inspect: record the affected Docker resource, the command that proves state and the rollback path.
  • 04. capture logs and exit code: record the affected Docker resource, the command that proves state and the rollback path.
  • 05. sketch the network path: record the affected Docker resource, the command that proves state and the rollback path.
  • 06. check the volume lifecycle: record the affected Docker resource, the command that proves state and the rollback path.
  • 07. assess image provenance: record the affected Docker resource, the command that proves state and the rollback path.
  • 08. distinguish tag and digest: record the affected Docker resource, the command that proves state and the rollback path.
  • 09. explain build cache impact: record the affected Docker resource, the command that proves state and the rollback path.
  • 10. write down rollback or cleanup path: record the affected Docker resource, the command that proves state and the rollback path.
  • 11. name the security impact: record the affected Docker resource, the command that proves state and the rollback path.
  • 12. rate the operational risk: record the affected Docker resource, the command that proves state and the rollback path.
  • 13. document context and desired state: record the affected Docker resource, the command that proves state and the rollback path.
  • 14. explain the command before running it: record the affected Docker resource, the command that proves state and the rollback path.
  • 15. prove current state with inspect: record the affected Docker resource, the command that proves state and the rollback path.
  • 16. capture logs and exit code: record the affected Docker resource, the command that proves state and the rollback path.
  • 17. sketch the network path: record the affected Docker resource, the command that proves state and the rollback path.
  • 18. check the volume lifecycle: record the affected Docker resource, the command that proves state and the rollback path.
  • 19. assess image provenance: record the affected Docker resource, the command that proves state and the rollback path.
  • 20. distinguish tag and digest: record the affected Docker resource, the command that proves state and the rollback path.
  • 21. explain build cache impact: record the affected Docker resource, the command that proves state and the rollback path.
  • 22. write down rollback or cleanup path: record the affected Docker resource, the command that proves state and the rollback path.
  • 23. name the security impact: record the affected Docker resource, the command that proves state and the rollback path.
  • 24. rate the operational risk: record the affected Docker resource, the command that proves state and the rollback path.
  • 25. document context and desired state: record the affected Docker resource, the command that proves state and the rollback path.
  • 26. explain the command before running it: record the affected Docker resource, the command that proves state and the rollback path.
  • 27. prove current state with inspect: record the affected Docker resource, the command that proves state and the rollback path.
  • 28. capture logs and exit code: record the affected Docker resource, the command that proves state and the rollback path.
  • 29. sketch the network path: record the affected Docker resource, the command that proves state and the rollback path.
  • 30. check the volume lifecycle: record the affected Docker resource, the command that proves state and the rollback path.
  • 31. assess image provenance: record the affected Docker resource, the command that proves state and the rollback path.
  • 32. distinguish tag and digest: record the affected Docker resource, the command that proves state and the rollback path.
  • 33. explain build cache impact: record the affected Docker resource, the command that proves state and the rollback path.
  • 34. write down rollback or cleanup path: record the affected Docker resource, the command that proves state and the rollback path.
04 / 07

Practice Appendix: Example Docker Socket Risk

This appendix provides a backlog for longer trainings, reviews and repetition. Each task is deliberately small so it can be verified and discussed independently.

A001. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: document context and desired state and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A002. Docker CLI

  • Task: explain the command before running it and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A003. Docker Engine

  • Task: prove current state with inspect and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A004. Dockerfile

  • Task: capture logs and exit code and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A005. Compose

  • Task: sketch the network path and explicitly relate the observation to Compose.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A006. Registry

  • Task: check the volume lifecycle and explicitly relate the observation to Registry.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A007. Security

  • Task: assess image provenance and explicitly relate the observation to Security.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A008. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: distinguish tag and digest and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A009. Docker CLI

  • Task: explain build cache impact and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A010. Docker Engine

  • Task: write down rollback or cleanup path and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A011. Dockerfile

  • Task: name the security impact and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A012. Compose

  • Task: rate the operational risk and explicitly relate the observation to Compose.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A013. Registry

  • Task: document context and desired state and explicitly relate the observation to Registry.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A014. Security

  • Task: explain the command before running it and explicitly relate the observation to Security.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A015. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: prove current state with inspect and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A016. Docker CLI

  • Task: capture logs and exit code and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A017. Docker Engine

  • Task: sketch the network path and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A018. Dockerfile

  • Task: check the volume lifecycle and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A019. Compose

  • Task: assess image provenance and explicitly relate the observation to Compose.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A020. Registry

  • Task: distinguish tag and digest and explicitly relate the observation to Registry.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A021. Security

  • Task: explain build cache impact and explicitly relate the observation to Security.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A022. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: write down rollback or cleanup path and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A023. Docker CLI

  • Task: name the security impact and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A024. Docker Engine

  • Task: rate the operational risk and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A025. Dockerfile

  • Task: document context and desired state and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A026. Compose

  • Task: explain the command before running it and explicitly relate the observation to Compose.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A027. Registry

  • Task: prove current state with inspect and explicitly relate the observation to Registry.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A028. Security

  • Task: capture logs and exit code and explicitly relate the observation to Security.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A029. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: sketch the network path and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A030. Docker CLI

  • Task: check the volume lifecycle and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A031. Docker Engine

  • Task: assess image provenance and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A032. Dockerfile

  • Task: distinguish tag and digest and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A033. Compose

  • Task: explain build cache impact and explicitly relate the observation to Compose.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A034. Registry

  • Task: write down rollback or cleanup path and explicitly relate the observation to Registry.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A035. Security

  • Task: name the security impact and explicitly relate the observation to Security.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A036. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: rate the operational risk and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A037. Docker CLI

  • Task: document context and desired state and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A038. Docker Engine

  • Task: explain the command before running it and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A039. Dockerfile

  • Task: prove current state with inspect and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A040. Compose

  • Task: capture logs and exit code and explicitly relate the observation to Compose.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A041. Registry

  • Task: sketch the network path and explicitly relate the observation to Registry.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A042. Security

  • Task: check the volume lifecycle and explicitly relate the observation to Security.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A043. Socket-Mounts, CI-Risiken und Schutzmaßnahmen

  • Task: assess image provenance and explicitly relate the observation to Socket-Mounts, CI-Risiken und Schutzmaßnahmen.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A044. Docker CLI

  • Task: distinguish tag and digest and explicitly relate the observation to Docker CLI.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A045. Docker Engine

  • Task: explain build cache impact and explicitly relate the observation to Docker Engine.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.

A046. Dockerfile

  • Task: write down rollback or cleanup path and explicitly relate the observation to Dockerfile.
  • Evidence: Write down at least one Docker command, one expected result and one limit of that evidence.
  • Operations question: What would a wrong assumption change in a CI runner, on a developer workstation and on a shared host?
  • Security question: Which permission, secret or host path is most sensitive in this step?
  • Cleanup: Describe which containers, images, networks, volumes or temporary files must be removed.
05 / 07

Official Sources and Scope

The material is aligned with public Docker documentation. When the workshop mentions external tools around Docker Engine, those tools are presented as adjacent operational practice, not as Docker Engine features.

  • Docker Engine: https://docs.docker.com/engine/
  • Dockerfile Reference: https://docs.docker.com/reference/dockerfile/
  • Compose File Reference: https://docs.docker.com/reference/compose-file/
  • Compose Specification: https://github.com/compose-spec/compose-spec/blob/master/spec.md
  • Docker Engine Security: https://docs.docker.com/engine/security/
  • Docker Rootless Mode: https://docs.docker.com/engine/security/rootless/
  • Protect the Docker Daemon Socket: https://docs.docker.com/engine/security/protect-access/
  • Docker Build Best Practices: https://docs.docker.com/build/building/best-practices/
  • Docker Training: https://www.docker.com/trainings/
06 / 07

Additional Review Drills

Use these drills when the primary task is complete and the learner needs another pass over operational reasoning. They are intentionally evidence-oriented and can be answered without inventing platform behavior.

Drill 01: image provenance

  • State which Docker object or host boundary is affected by image provenance.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 02: build context

  • State which Docker object or host boundary is affected by build context.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 03: layer ordering

  • State which Docker object or host boundary is affected by layer ordering.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 04: container user

  • State which Docker object or host boundary is affected by container user.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 05: mounts and volumes

  • State which Docker object or host boundary is affected by mounts and volumes.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 06: bridge network

  • State which Docker object or host boundary is affected by bridge network.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 07: port publishing

  • State which Docker object or host boundary is affected by port publishing.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 08: Compose configuration

  • State which Docker object or host boundary is affected by Compose configuration.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 09: daemon socket

  • State which Docker object or host boundary is affected by daemon socket.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 10: registry access

  • State which Docker object or host boundary is affected by registry access.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 11: rootless mode

  • State which Docker object or host boundary is affected by rootless mode.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 12: seccomp and capabilities

  • State which Docker object or host boundary is affected by seccomp and capabilities.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 13: logs and events

  • State which Docker object or host boundary is affected by logs and events.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 14: cleanup and rollback

  • State which Docker object or host boundary is affected by cleanup and rollback.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 15: image provenance

  • State which Docker object or host boundary is affected by image provenance.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.

Drill 16: build context

  • State which Docker object or host boundary is affected by build context.
  • Name one command that produces evidence and one field in the output that matters.
  • Explain what can be concluded from that evidence and what cannot be concluded from it.
  • Describe the safest cleanup path for a shared training host.
07 / 07

DKR · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.