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
Mount a volume to containers when executing RUN instructions during the build. This is equivalent to the --volume option of podman build, and generally has the form [[SOURCE-VOLUME|HOST-DIR:]CONTAINER-DIR[:OPTIONS]].
If SOURCE-VOLUME starts with ., Quadlet resolves the path relative to the location of the unit file.
Special case:
If SOURCE-VOLUME ends with .volume, Quadlet will look for the corresponding .volume Quadlet unit. If found, Quadlet will use the name of the Volume set in the Unit, otherwise, systemd-$name is used. The generated systemd service contains a dependency on the service unit generated for that .volume unit, or on $name-volume.service if the .volume unit is not found. Note: the corresponding .volume file must exist.
However, podman-build manual says (and in reality this is how it works) that only HOST-DIR is supported, not referencing a SOURCE-VOLUME.
Steps to reproduce the issue
Steps to reproduce the issue
podman create volume test
Reference volume test in build ([Build] Volume=test:/test)
Describe the results you received
systemctl start of the build unit fails
Describe the results you expected
Docs should not describe referencing SOURCE-VOLUME
podman info output
host:
arch: amd64buildahVersion: 1.38.1cgroupControllers:
- cpuset
- cpu
- io
- memory
- hugetlb
- pids
- rdma
- misccgroupManager: systemdcgroupVersion: v2conmon:
package: conmon-2.1.12-3.fc41.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 99.87systemPercent: 0.07userPercent: 0.06cpus: 64databaseBackend: sqlitedistribution:
distribution: fedoraversion: "41"eventLogger: journaldfreeLocks: 2022hostname: fedoraidMappings:
gidmap: nulluidmap: nullkernel: 6.12.8-200.fc41.x86_64linkmode: dynamiclogDriver: journaldmemFree: 138684092416memTotal: 270315503616networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.13.1-1.fc41.x86_64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.13.1package: netavark-1.13.1-1.fc41.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.13.1ociRuntime:
name: crunpackage: crun-1.19.1-1.fc41.x86_64path: /usr/bin/crunversion: |- crun version 1.19.1 commit: 3e32a70c93f5aa5fea69b50256cca7fd4aa23c80 rundir: /run/user/0/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20250121.g4f2c8e7-2.fc41.x86_64version: | pasta 0^20250121.g4f2c8e7-2.fc41.x86_64 Copyright Red Hat GNU General Public License, version 2 or later <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.remoteSocket:
exists: truepath: /run/podman/podman.sockrootlessNetworkCmd: pastasecurity:
apparmorEnabled: falsecapabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOTrootless: falseseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: trueserviceIsRemote: falseslirp4netns:
executable: ""package: ""version: ""swapFree: 8589930496swapTotal: 8589930496uptime: 44h 31m 11.00s (Approximately 1.83 days)variant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.iostore:
configFile: /etc/containers/storage.confcontainerStore:
number: 7paused: 0running: 7stopped: 0graphDriverName: zfsgraphOptions:
zfs.mountopt: nodevgraphRoot: /var/lib/containers/storagegraphRootAllocated: 1760121192448graphRootUsed: 11141120graphStatus:
Compression: "on"Parent Dataset: *Parent Quota: "no"Space Available: "1760110075904"Space Used By Parent: "939257856"Zpool: *Zpool Health: ONLINEimageCopyTmpDir: /var/tmpimageStore:
number: 13runRoot: /run/containers/storagetransientStore: falsevolumePath: /var/lib/containers/storage/volumesversion:
APIVersion: 5.3.2Built: 1737504000BuiltTime: Wed Jan 22 03:00:00 2025GitCommit: ""GoVersion: go1.23.4Os: linuxOsArch: linux/amd64Version: 5.3.2
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered:
Issue Description
Manual says
However, podman-build manual says (and in reality this is how it works) that only HOST-DIR is supported, not referencing a SOURCE-VOLUME.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
systemctl start of the build unit fails
Describe the results you expected
Docs should not describe referencing SOURCE-VOLUME
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: