getporter/porter

Failed to publish to docker registry

Closed this issue · 4 comments

AGMETEOR commented

Describe the bug

Failed to publish bundle to hub.docker.com

To Reproduce

Steps to reproduce the behavior:

  1. Run porter publish --registry hub.docker.com or porter publish --registry hub.docker.com/r/agmeteor
  2. Use the default porter.yaml file from the porter-hello example https://getporter.org/getting-started/create-bundle/
  3. See error
reference not found (hub.docker.com/r/agmeteor/porter-hello:v0.1.0)
Pushing bundle image...
The push refers to repository [hub.docker.com/r/agmeteor/porter-hello]
5f70bf18a086: Preparing
d9aa768d9bdd: Preparing
c6d0867dbe69: Preparing
e5ec85adb079: Preparing
318f55ac9136: Preparing
0a3fec6d3c7d: Preparing
b85f69b0b2d2: Preparing
f9f342925acf: Preparing
a5f82b0a6298: Preparing
34f03f266053: Preparing
0a3fec6d3c7d: Waiting
b85f69b0b2d2: Waiting
f9f342925acf: Waiting
a5f82b0a6298: Waiting
34f03f266053: Waiting
failed to stream docker push stdout: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!doctype html>\n<html lang=\"en\">\n\n<head>\n ...

Expected behavior

I expected to see my oci artifact on docker registry

Version

porter v1.0.14 (0e739d88)

itsaviral2609 commented

Screenshot from 2023-07-23 00-23-40

Tried this issue, worked fine for me!

Here is the porter.yaml file

Screenshot from 2023-07-23 01-46-07

AGMETEOR commented

Thanks @itsaviral2609 . You're right it works just fine using porter publish --registry=docker.io/<my_reg_name>. I don't know why I thought hub.docker.com was the name of the registry.

AGMETEOR commented

I'll close this now.

itsaviral2609 commented

cool! Happy yo help @AGMETEOR :)