You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quadlet supports templated containers (name@.container), and it's often the case that each instantiated container would need its own separate volume storage, but Quadlet doesn't seem to have support for that. This heavily limits the usefulness of the templating feature.
Run /usr/lib/systemd/user-generators/podman-user-generator -dryrun
Describe the results you received
The generated volume template is foo@-volume.service rather than foo-volume@.service, and the generated volume instance is foo@alpha-volume.service rather than foo-volume@alpha.service
Error while generating template and instance for foo@.container:
quadlet-generator[14324]: converting "foo@.container": requested Quadlet source foo@%i.volume was not found
converting "foo@alpha.container": requested Quadlet source foo@%i.volume was not found
Describe the results you expected
Quadlet should generate proper template and instance service files for foo@.volume, and it should be possible to reference them from foo@.container.
You can play around with trying to set a custom templated volume name in ~/.config/containers/systemd/foo@.volume, but as far as my imagination has taken me, nothing worked.
The text was updated successfully, but these errors were encountered:
Issue Description
Quadlet supports templated containers (
name@.container
), and it's often the case that each instantiated container would need its own separate volume storage, but Quadlet doesn't seem to have support for that. This heavily limits the usefulness of the templating feature.Steps to reproduce the issue
/usr/lib/systemd/user-generators/podman-user-generator -dryrun
Describe the results you received
foo@-volume.service
rather thanfoo-volume@.service
, and the generated volume instance isfoo@alpha-volume.service
rather thanfoo-volume@alpha.service
foo@.container
:Describe the results you expected
Quadlet should generate proper template and instance service files for
foo@.volume
, and it should be possible to reference them fromfoo@.container
.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
ArchLinux x86_64. Everything is latest.
Additional information
You can play around with trying to set a custom templated volume name in
~/.config/containers/systemd/foo@.volume
, but as far as my imagination has taken me, nothing worked.The text was updated successfully, but these errors were encountered: