Skip to content

fix broken link legacy_communication host drivers question #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lacatoire merged 1 commit into from
Jan 20, 2026
Merged

fix broken link legacy_communication host drivers question #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/1_Orchestration/legacy_communication.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ questions:
- { value: 'Mount a volume from the legacy system', correct: false }
- { value: 'Use a static IP assignment or run the container with host networking', correct: true }
- { value: 'Use dynamic IP allocation via overlay network', correct: false }
help: https://docs.docker.com/network/network-tutorial-host/
help: https://docs.docker.com/engine/network/drivers/host/

- uuid: 36efbf34-91e6-49fd-9398-3948ae194c2c
question: Which practice helps decouple Dockerized applications from legacy systems during a migration process?
Expand Down