Quadlet .build file Pull=always option is not working

[schreibubi]

Issue Description

I'm using the following .build file to build an updated container:

[Build]
Pull=always
ImageTag=localhost/nextcloudplus
SetWorkingDirectory=/fs/datassd/nextcloudUpdatedImage/

Running

systemctl --user start nextcloudplus-build.service 

fails with:

nextcloudplus-build[67897]: Error: accepts at most 1 arg(s), received 2

Contents of the generated nextcloudplus-build.service file:

# /run/user/1000/systemd/generator/nextcloudplus-build.service
# Automatically generated by /usr/lib/systemd/user-generators/podman-user-generator
# 
[X-Build]
Pull=always
ImageTag=localhost/nextcloudplus
SetWorkingDirectory=/fs/datassd/nextcloudUpdatedImage/


[Unit]
Wants=podman-user-wait-network-online.service
After=podman-user-wait-network-online.service
RequiresMountsFor=%t/containers
SourcePath=/home/joerg/.config/containers/systemd/nextcloudplus.build

[Service]
ExecStart=/usr/bin/podman build --pull always --tag localhost/nextcloudplus /fs/datassd/nextcloudUpdatedImage/
SyslogIdentifier=%N
Type=oneshot

# /usr/lib/systemd/user/service.d/10-timeout-abort.conf
# This file is part of the systemd package.
# See https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer.
#
# To facilitate debugging when a service fails to stop cleanly,
# TimeoutStopFailureMode=abort is set to "crash" services that fail to stop in
# the time allotted. This will cause the service to be terminated with SIGABRT
# and a coredump to be generated.
#
# To undo this configuration change, create a mask file:
#   sudo mkdir -p /etc/systemd/user/service.d
#   sudo ln -sv /dev/null /etc/systemd/user/service.d/10-timeout-abort.conf

[Service]
TimeoutStopFailureMode=abort

When I try to run the command from ExecStart myself, I get the same error. If I execute instead using --pull=always it is working

So I assume that at some point podman started expecting the --pull=always instead of --pull always

Steps to reproduce the issue

See above

Describe the results you received

Error

Describe the results you expected

Updated image

podman info output

host:
  arch: amd64
  buildahVersion: 1.38.0
  cgroupControllers:
  - cpu
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.12-3.fc41.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.12, commit: '
  cpuUtilization:
    idlePercent: 89.78
    systemPercent: 2.05
    userPercent: 8.17
  cpus: 12
  databaseBackend: boltdb
  distribution:
    distribution: fedora
    version: "41"
  eventLogger: journald
  freeLocks: 1829
  hostname: mthood.schreibubi.home.arpa
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 6.11.8-300.fc41.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 713822208
  memTotal: 33375813632
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.13.1-1.fc41.x86_64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.13.1
    package: netavark-1.13.0-1.fc41.x86_64
    path: /usr/libexec/podman/netavark
    version: netavark 1.13.0
  ociRuntime:
    name: crun
    package: crun-1.18.1-1.fc41.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.18.1
      commit: c41f034fdbb9742c395085fc98459c94ad1f9aae
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20241121.g238c69f-1.fc41.x86_64
    version: |
      pasta 0^20241121.g238c69f-1.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: true
    path: /run/user/1000/podman/podman.sock
  rootlessNetworkCmd: pasta
  security:
    apparmorEnabled: false
    capabilities: 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_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.3.1-1.fc41.x86_64
    version: |-
      slirp4netns version 1.3.1
      commit: e5e368c4f5db6ae75c2fce786e31eef9da6bf236
      libslirp: 4.8.0
      SLIRP_CONFIG_VERSION_MAX: 5
      libseccomp: 2.5.5
  swapFree: 72585306112
  swapTotal: 72589762560
  uptime: 5h 39m 35.00s (Approximately 0.21 days)
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /home/joerg/.config/containers/storage.conf
  containerStore:
    number: 39
    paused: 0
    running: 39
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/joerg/.local/share/containers/storage
  graphRootAllocated: 929760804864
  graphRootUsed: 38617509888
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Supports shifting: "false"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 65
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/joerg/.local/share/containers/storage/volumes
version:
  APIVersion: 5.3.1
  Built: 1732147200
  BuiltTime: Thu Nov 21 01:00:00 2024
  GitCommit: ""
  GoVersion: go1.23.3
  Os: linux
  OsArch: linux/amd64
  Version: 5.3.1

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

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

[Luap99]

Duplicate of #24599