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
Support for unmask as security option via --security-opt flag was implemented in containers/podman#8408. However, it seems to be missing from the build subcommand as documentation only states
Running ``podman build` in a Podman-in-Podman scenarion (e.g. CI pipeline) requires this in order to avoid having to mount /proc to /proc via command line which does not allow for unmasking selective paths.
$ podman infohost:
arch: amd64buildahVersion: 1.37.5cgroupControllers:
- cpuset
- cpu
- io
- memory
- hugetlb
- pidscgroupManager: cgroupfscgroupVersion: v2conmon:
package: conmon-2.1.12-2.fc40.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 99.46systemPercent: 0.22userPercent: 0.32cpus: 8databaseBackend: sqlitedistribution:
distribution: fedoravariant: containerversion: "40"eventLogger: filefreeLocks: 2048hostname: runner-smfycxu4q-project-809-concurrent-0idMappings:
gidmap: nulluidmap: nullkernel: 5.14.0-503.14.1.el9_5.x86_64linkmode: dynamiclogDriver: k8s-filememFree: 8688377856memTotal: 16499392512networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.12.2-2.fc40.x86_64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.12.2package: netavark-1.12.2-1.fc40.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.12.2ociRuntime:
name: crunpackage: crun-1.17-1.fc40.x86_64path: /usr/bin/crunversion: |- crun version 1.17 commit: 000fa0d4eeed8938301f3bcf8206405315bc1017 rundir: /run/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20241030.gee7d0b6-1.fc40.x86_64version: | pasta 0^20241030.gee7d0b6-1.fc40.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: falsepath: /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: falseserviceIsRemote: falseslirp4netns:
executable: ""package: ""version: ""swapFree: 4249358336swapTotal: 4294963200uptime: 20h 4m 57.00s (Approximately 0.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: 0paused: 0running: 0stopped: 0graphDriverName: vfsgraphOptions:
vfs.imagestore: /usr/lib/containers/storagegraphRoot: /var/lib/containers/storagegraphRootAllocated: 519676362752graphRootUsed: 11840548864graphStatus: {}imageCopyTmpDir: /var/tmpimageStore:
number: 0runRoot: /run/containers/storagetransientStore: falsevolumePath: /var/lib/containers/storage/volumesversion:
APIVersion: 5.2.5Built: 1729814400BuiltTime: Fri Oct 25 00:00:00 2024GitCommit: ""GoVersion: go1.22.7Os: linuxOsArch: linux/amd64Version: 5.2.5
Podman in a container
Yes
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Podman called from ansible-builder within quay.io/containers/community-ansible-dev-tools:lastest running in a GitLab CI pipeline job using Docker Executor with Podman 5.2.2 as container engine on a RHEL9 host.
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
Good Afternoon.
Support for unmask as security option via
--security-opt
flag was implemented in containers/podman#8408. However, it seems to be missing from thebuild
subcommand as documentation only statesand specifying this option results in
Running ``podman build` in a Podman-in-Podman scenarion (e.g. CI pipeline) requires this in order to avoid having to mount /proc to /proc via command line which does not allow for unmasking selective paths.
Steps to reproduce the issue
podman build --security-opt unmask=/proc -f Containerfile
Describe the results you received
Error: invalid --security-opt 2: "unmask=ALL
Describe the results you expected
Podman builds the container image.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Podman called from ansible-builder within quay.io/containers/community-ansible-dev-tools:lastest running in a GitLab CI pipeline job using Docker Executor with Podman 5.2.2 as container engine on a RHEL9 host.
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: