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.

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

Adding comments for container options in qm.container #678

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ilimarx
Copy link

@ilimarx ilimarx commented Dec 19, 2024

No description provided.

@@ -35,10 +35,24 @@ LimitNOFILE=65536
TasksMax=50%

[Container]
# AddCapability
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would recommend here to use man quadlet also for details

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried to copy some details from man quadlet, hope it's better now

Copy link
Collaborator

@Yarboa Yarboa Jan 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding this link to upstream doc
https://docs.podman.io/en/v4.4/markdown/podman-systemd.unit.5.html#addcapability
for each Capability

Or that one, it is more accurate
man quadlet | awk '/AddCapability=$/,/^$/'

MHO it more accurate then copy paste content of changing description.
It could also be automated to check if parameters were changed,
I mean file parameters vs existence in manual

# AddCapability
# -------------
# Grants all capabilities to the container, increasing flexibility but significantly
# reducing security.
AddCapability=all
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

qm.container Outdated
# Unmask
# -------
# Unmasks all systemd services for the container, overriding masking that prevents
# access to specific services.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as below

qm.container Outdated

# Rootfs
# ------
# Defines the root filesystem location for the container.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would specify the QM rootfs partition

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've specified the default path for rootfs

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see lower explanation related the usage of container

# Rootfs
# ------
# Defines the root filesystem location for the container.
# The '${ROOTFS}' variable should point to a valid filesystem path.
Rootfs=${ROOTFS}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see previous one is it a container or partitioned filesystem?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what you mean here. Please check the changes

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I will try to explain there is a difference between running containerized podman and podman as part of file system
So in QM, container tools enables process isolation in the save filesystem and filesystem partition is isolated by disks

This i why it looks to me more logical to use disk instead of container
Consider using this
Defines the root filesystem location for QM partition.
instead
Defines the root filesystem location for the container.

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.

2 participants