[DOC] [QA] Podman installation instructions wrongs

Description

https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/install-pmm-server/baremetal/podman/index.html#install

The service should use %h, instead of ~. Also, it should come with a note that to start it on 443/tcp changes to net.ipv4.ip_unprivileged_port_start will be needed (even if it’s in the linked document above).

How to test

Validation on RHEL 9, Amazon Linux needed to proof that our instructions work as expected

How to document

None

Activity

Show:

Nurlan Moldomurov March 3, 2025 at 1:08 PM

, can you check AMI/OVF scripts that prepares OS to run podman with commands in documentation

Ondrej Patocka February 18, 2025 at 1:53 PM

Refinement notes
- preconfig validation - can help to validate

Iwo Panowicz February 5, 2025 at 9:32 AM

Watchtower one would be something like:

[Unit] Description=watchtower Wants=network-online.target After=network-online.target After=nss-user-lookup.target nss-lookup.target After=time-sync.target Requires=podman.socket [Service] EnvironmentFile=%h/.config/systemd/user/watchtower.env Restart=on-failure RestartSec=20 ExecStart=/usr/bin/podman run --rm --replace=true --name %N \ -v ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/docker.sock \ --env-file=%h/.config/systemd/user/watchtower.env \ --net pmm_default \ --security-opt label=type:container_runtime_t \ --cap-add=net_admin,net_raw \ ${WATCHTOWER_IMAGE} ExecStop=/usr/bin/podman stop -t 10 %N [Install] WantedBy=default.target

however the container_runtime_t would be a bit debatable.

Details

Assignee

Reporter

Priority

Needs QA

Yes

Needs Doc

Yes

Planned Version/s

Story Points

Sprint

Affects versions

Smart Checklist

Created February 5, 2025 at 8:59 AM
Updated 20 hours ago

Flag notifications