Skip to content
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

Jump to bottom

Choose OCIRuntime implementation #2

Open
mgjm opened this issue Jun 20, 2023 · 1 comment
Open

Choose OCIRuntime implementation #2

mgjm opened this issue Jun 20, 2023 · 1 comment
Labels
cleanup Steps required before merging into upstream
Milestone
1: Basic Functions

Comments

@mgjm
Copy link
Owner

mgjm commented Jun 20, 2023

The podman executable needs to decide whether to use the existing ConmonOCIRuntime or the new ConmonRSOCIRuntime.

Solutions:

  • New config option in containers.conf
  • Automatic detection based on installed binaries
  • Both (config with default = auto)
@mgjm mgjm added this to the 1: Basic Functions milestone Jun 20, 2023
@mgjm mgjm mentioned this issue Jun 20, 2023
Open
@mgjm
Copy link
Owner Author

mgjm commented Jun 20, 2023

Current workaround in mgjm-fork/podman@c39ab62:

Podman already supports different OCI runtimes, configurable via containers.conf. And all runtimes specified in [engine.runtimes] get added to the Runtime.ociRuntimes map in podman.

The new implementation using conmon-rs get added as well, with a conmon-rs: prefix.

The following containers.conf enables the new ConmonRSOCIRuntime with crun:

[engine]
runtime = "conmon-rs:crun"

@mgjm mgjm added the cleanup Steps required before merging into upstream label Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup Steps required before merging into upstream
Projects
None yet
Milestone
1: Basic Functions
Development

No branches or pull requests
1 participant
@mgjm