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

Podman build --cache-from: Error: failed to parse query parameter 'cacheFrom': "111257922624.dkr.ecr.us-east-1.amazonaws.com/cache": invalid character 'd' after decimal point in numeric literal #24915

Open
ofekifergan opened this issue Dec 29, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote

Comments

@ofekifergan
Copy link

ofekifergan commented Dec 29, 2024

Issue Description

When trying to build image with podman using cache I am getting:

Podman build --cache-from: Error: failed to parse query parameter 'cacheFrom': "111257922624.dkr.ecr.us-east-1.amazonaws.com/cache": invalid character 'd' after decimal point in numeric literal

Steps to reproduce the issue

Steps to reproduce the issue

  1. Enable podman socket api (tcp)
  2. Run: podman build -t 111257922624.dkr.ecr.us-east-1.amazonaws.com/server:latest -f Dockerfile . --cache-from 111257922624.dkr.ecr.us-east-1.amazonaws.com/cache --format docker
  3. Make sure you are using aws ecr (contains numbers)

Describe the results you received

Error: failed to parse query parameter 'cacheFrom': "111257922624.dkr.ecr.us-east-1.amazonaws.com/cache": invalid character 'd' after decimal point in numeric literal

Describe the results you expected

I expect the build to be successful using remote socket and caching in AWS ECR

podman info output

host:
  arch: amd64
  buildahVersion: 1.38.0
  cgroupControllers:
  - cpuset
  - cpu
  - cpuacct
  - blkio
  - memory
  - devices
  - freezer
  - net_cls
  - perf_event
  - net_prio
  - hugetlb
  - pids
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: conmon-2.1.12-3.fc41.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.12, commit: '
  cpuUtilization:
    idlePercent: 93.37
    systemPercent: 1.92
    userPercent: 4.72
  cpus: 4
  distribution:
    distribution: fedora
    variant: container
    version: "41"
  eventLogger: file
  hostname: xxx
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.10.219-208.866.amzn2.x86_64
  linkmode: dynamic
  logDriver: k8s-file
  memFree: 7441014784
  memTotal: 16393895936
  networkBackend: netavark
  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/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: tcp:0.0.0.0:8080
  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: false
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: true
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 0
  swapTotal: 0
  uptime: 4h 29m 17.00s (Approximately 0.17 days)
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
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.imagestore: /usr/lib/containers/storage
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-1.13-2.fc41.x86_64
      Version: |-
        fusermount3 version: 3.16.2
        fuse-overlayfs: version 1.13-dev
        FUSE library version 3.16.2
        using FUSE kernel interface version 7.38
    overlay.mountopt: nodev,fsync=0
  graphRoot: /var/lib/containers/storage
  graphRootAllocated: 161048670208
  graphRootUsed: 15952273408
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Supports shifting: "true"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 12
  runRoot: /run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 5.3.0
  Built: 1731456000
  BuiltTime: Wed Nov 13 00:00:00 2024
  GitCommit: ""
  GoVersion: go1.23.2
  Os: linux
  OsArch: linux/amd64
  Version: 5.3.0

Podman in a container

Yes

Privileged Or Rootless

Privileged

Upstream Latest Release

Yes

Additional environment details

CONTAINER_HOST="tcp://localhost:8080"

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@ofekifergan ofekifergan added the kind/bug Categorizes issue or PR as related to a bug. label Dec 29, 2024
@github-actions github-actions bot added the remote Problem is in podman-remote label Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote
Projects
None yet
Development

No branches or pull requests

1 participant