Skip to content

fix: recognize openvzve container runtime#2801

Open
raman1236 wants to merge 1 commit into
puppetlabs:mainfrom
raman1236:fix/openvzve-container-runtime
Open

fix: recognize openvzve container runtime#2801
raman1236 wants to merge 1 commit into
puppetlabs:mainfrom
raman1236:fix/openvzve-container-runtime

Conversation

@raman1236

Copy link
Copy Markdown

Description

Recognize openvzve as a valid container runtime in the Containers resolver.

Problem

Since facter 4.8.0, running inside an OpenVZ virtual environment (/proc/1/environ contains container=openvzve) returns no virtual or hypervisor facts because openvzve is not handled in the read_environ case statement.

Fix

Add when 'openvzve' case that maps to vm = 'openvz' for consistency with the existing OpenVZ resolver (lib/facter/resolvers/open_vz.rb).

Fixes #2784

Add 'openvzve' to the container runtime case statement in the
Containers resolver. OpenVZ virtual environments set container=openvzve
in /proc/1/environ, but this was not handled after the runtime
detection was refactored in 4.8.0.

Map 'openvzve' to the 'openvz' virtual fact for consistency with
the existing OpenVZ resolver.

Fixes puppetlabs#2784
@raman1236 raman1236 requested a review from a team as a code owner April 5, 2026 23:41
@raman1236

Copy link
Copy Markdown
Author

Friendly ping — this PR adds recognition for the openvzve container runtime in facter's virtualization detection. Small and straightforward fix. Would appreciate a review. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unsupported container runtime 'openvzve' with facter 4.8.0+

2 participants