podman push to acr always fails with Error: unexpected EOF

Payyd tech works LLC 0 Reputation points
2024-08-06T03:04:45.4633333+00:00

Hello, am using ACR in standard plan. I have a small web app which is served in azure container app. Am trying to deploy new image to azure container registry and push command always failing with Error: unexpected EOF

It was working few weeks ago and not sure why it stopped working. All the example provided in azure is only using docker which we don't want to use and picked alternative podman.

Below are some logs from podman tag and push commands...
Building version v1

STEP 1/10: FROM --platform=linux/amd64 golang:1.22.5

Resolving "golang" using unqualified-search registries (/etc/containers/registries.conf.d/999-podman-machine.conf)

Trying to pull docker.io/library/golang:1.22.5...

Getting image source signatures

Copying blob sha256:ca4e5d6727252f0dbc207fbf283cb95e278bf562bda42d35ce6c919583a110a0

Copying blob sha256:ddb1467b736f6b84ad01493f98b050ed46efd37c54e4307fffc56ed028fdeab6

Copying blob sha256:5e53f8e7a11a56a5e15226ca5d9a2f740b0e5aa702ca2616748207531fee32ca

Copying blob sha256:10d643a5fa823cd013a108b2076f4d2edf1b2a921f863b533e83ea5ed8d09bd4

Copying blob sha256:32a2f51ff3dde07bfa1ce35b5597b2d97295e64a461d98e696feda7b25a6dc5f

Copying blob sha256:30b93c12a9c9326732b35d9e3ebe57148abe33f8fa6e25ab76867410b0ccf876

Copying blob sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1

Copying config sha256:a61b645b609b758e4c0a9c57efbba8ccc610abb4d96544cedd8411aa1c9e4b09

Writing manifest to image destination

STEP 2/10: WORKDIR /app

--> 142f6fccdd41

STEP 3/10: COPY go.mod ./

--> 9449c36c6ec6

STEP 4/10: RUN go mod download

--> 520ef79fe448

STEP 5/10: COPY . .

--> 64efa27c82ad

STEP 6/10: RUN CGO_ENABLED=0 GOOS=linux go build -o /go-podman-demo

--> 4c9b550b25bb

STEP 7/10: COPY templates /app/templates

--> 6ad3914892fb

STEP 8/10: COPY static /app/static

--> 6ed5e8b412a5

STEP 9/10: EXPOSE 80

--> 6b70b4f12a5b

STEP 10/10: CMD [ "/go-podman-demo" ]

COMMIT my-image

--> 094fce7b1e5b

[Warning] one or more build args were not consumed: [BUILDPLATFORM]

Successfully tagged localhost/my-image:latest

094fce7b1e5b0377da02802330173abfeb05891a4608d9e9c6eb27a1d98a6f69

building image succeeded

TAGGING REMOTE

PUSH TAGGED NOW

Getting image source signatures

Copying blob sha256:7cfafa82cfd2b6a92aeb90093e38fb88fa4377948d71bd970d11a51bae16d2f1

Copying blob sha256:83827c332bb06d50c91b5c06a1ac57b3add280fa3b098a0d57e29b96456ef6c6

Copying blob sha256:0905150af928fc88e784dcad5ba98d5f3c2ab28c51c30ac7c7aa8599100cf02f

Copying blob sha256:0c0bb6fe83a9384a149f8bda5200950fdab6eb32fa5b4e35e4285d2c9253a98a

Copying blob sha256:03efbc301ddfd093c26664436038e18bda3ae48a7872d6ac01d5dfb06af403b3

Copying blob sha256:f6faf32734e0870d82ea890737958fe33ce9ddfed27b3b157576d2aadbab3322

Copying blob sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef

Copying blob sha256:c4f657f5a530713402fa22489bee5fdbaea8e1aa5e77c463a61a0868c38d1a32

Copying blob sha256:b58c6c7e15465a263bb4083b2affbf71b8f3712a7ede8f5968be83cb33eb177d

Error: unexpected EOF

PUSH TO GITHUB

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
446 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Nikhil Duserla 2,025 Reputation points Microsoft Vendor
    2024-08-09T08:49:33.9633333+00:00

    Hi @Payyd tech works LLC,

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    We understand from your query that you are experiencing an issue with pushing a new image to Azure Container Registry (ACR) using Podman, and you're getting an unexpected EOF error.

    We would recommend the following shared troubleshooting steps that I believe will help resolve the issue you reported.

    • Ensure that there are no network issues between your environment and the Azure Container Registry.

    ping <your-acr-registry-name>.azurecr.io

    curl -v https://<your-acr-registry-name>.azurecr.io/v2/

    • Ensure that you are using the latest version of Podman. Sometimes, updating to the latest version can resolve compatibility issues.
    • If you have access to another container registry, try pushing the image to that registry to see if the issue is specific to ACR.

    If you have any further queries, do let us know.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.