-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Docs] Suggestion to add information about environment #10095
base: main
Are you sure you want to change the base?
Conversation
I'm concerned this change will introduce more confusion than clarity. Running |
@laurazard that's true, "preserved" is the right word here 👍 Thanks! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10095 +/- ##
===========================================
- Coverage 76.98% 19.55% -57.44%
===========================================
Files 2 104 +102
Lines 252 9104 +8852
===========================================
+ Hits 194 1780 +1586
- Misses 51 7137 +7086
- Partials 7 187 +180 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Benjamin Balder Bach <benjamin@overtag.dk>
Co-authored-by: Laura Brehm <laurabrehm@hey.com> Signed-off-by: Benjamin Balder Bach <benjaoming@gmail.com>
Signed-off-by: Benjamin Balder Bach benjamin@overtag.dk
What I did
I wondered about what happens to a container's environment when you launch commands via
exec
. Is it preserved or do I have to re-do it.Turns out for me (Compose v2) it's nicely preserved.
Added a little general tip for debugging the environment on a running container.