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

fix: name of volume quadlet service should be basename-volume.service #119

Merged

Conversation

richm
Copy link
Contributor

@richm richm commented Jan 11, 2024

Cause: The code was using a volume quadlet service name of basename.volume.

Consequence: Attempting to start this service name would give an error such
as "Could not find the requested service NAME.volume: host"

Fix: The volume quadlet service name is changed to basename-volume.service

Result: The volume service can be started with no errors.

See https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#volume-units-volume
for more info.

Signed-off-by: Rich Megginson rmeggins@redhat.com

Cause: The code was using a volume quadlet service name of basename.volume.

Consequence: Attempting to start this service name would give an error such
as "Could not find the requested service NAME.volume: host"

Fix: The volume quadlet service name is changed to basename-volume.service

Result: The volume service can be started with no errors.

See https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#volume-units-volume
for more info.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
@richm
Copy link
Contributor Author

richm commented Jan 11, 2024

[citest]

@richm richm merged commit 5edd71e into linux-system-roles:main Jan 16, 2024
18 of 20 checks passed
@richm richm deleted the fix-quadlet-volume-service-name branch January 16, 2024 16:52
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.

None yet

1 participant