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
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
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
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
Issue Description
When trying to build image with podman using cache I am getting:
Steps to reproduce the issue
Steps to reproduce the issue
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
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
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
The text was updated successfully, but these errors were encountered: