Closed mbaldessari closed 6 years ago
We create a .containerenv
file instead (after some past debate on this subject - we're somewhat reluctant to use the Docker name). This is definitely not good for preexisting tools, though. @rhatdan are we still firm on leaving this as-is?
I've been down this path, too :wink: https://github.com/containers/libpod/issues/648
Ack thanks, I am fine with tweaking my code to use /run/.containerenv. Shall we close this as a dupe of https://github.com/containers/libpod/issues/648 ?
Is this a BUG REPORT or FEATURE REQUEST?:
[//]: # Uncomment only one, leave it on its own line:
[//]: kind bug
[//]: # kind feature
Description
Describe the results you expected: There are likely tools out there (I know we check this at least in puppet-pacemaker via a facter check) that rely on that file being available to have a very simple means to detect if we're running inside a container. Likely there are more tools out there relying on this.
This was tested on updated (as of today) F28.
Output of
podman version
:Output of
podman info
: