Test the connectivity to a Docker registry before creating it

[kwerle]

I tried to configure a private registry using the host url I docker log'ed in to - which was like

https://my.host.name/v2/

It turns out that portainer didn't like that, but gave no immediate feedback. Instead it said:

"Image from container: invalid reference format"

when I tried to add a new container.

I recommend that when you add a registry portainer tries to validate it. If that's not possible then it'd be nice for the failure message to be way more explicit. Maybe including some technical error information.

[deviantony]

You should probably try with https://my.host.name instead of https://my.host.name/v2/

I agree, we will try to test the connectivity before creating the registry.

[kwerle]

Yes, that is the fix. My point was that it wasn't clear what the issue was. A connectivity test would have nailed it at registry creation time - if that's possible... Thanks!

[zwx168238]

i got the same issue
my setting was like below
Registry URL https://njdocker1.nj.thundersoft.com
name harbor

then i want to use pull image
name njdocker1.nj.thundersoft.com/public/rsyslog:1.0
Registry harbor

i was setting the auth info and if i use docker pull njdocker1.nj.thundersoft.com/public/rsyslog:1.0 can pull the img from my own Registry

@deviantony this is my origin setting

[ncresswell]

You need to add the port number to the registry url... port 5000 is Docker default.. Rgds, Neil Cresswell On 20/09/2017, at 5:17 PM, zwx168238 <notifications@github.com<mailto:notifications@github.com>> wrote: i got the same issue my setting was like below Registry URL https://njdocker1.nj.thundersoft.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__njdocker1.nj.thundersoft.com&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=H99wJQGgBWkcoainkjvqEarIuUvyd7LMw--mBBb76rw&s=05gffEv0a9BEG9dhnOJVQ6Idmcy0-e1Qc4BDMsMSMHw&e=> name harbor then i want to use pull image name njdocker1.nj.thundersoft.com/public/rsyslog:1.0<http://njdocker1.nj.thundersoft.com/public/rsyslog:1.0> Registry harbor i was setting the auth info and if i use docker pull njdocker1.nj.thundersoft.com/public/rsyslog:1.0<http://njdocker1.nj.thundersoft.com/public/rsyslog:1.0> can pull the img from my own Registry — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_1182-23issuecomment-2D330809591&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=H99wJQGgBWkcoainkjvqEarIuUvyd7LMw--mBBb76rw&s=aEJdJjYz1FStqqcwPSyWlyv6KoimWQ9j0aDevWJMVjE&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrla8I91y6j95cuQrEc5TPPl7RFqQFks5skOZRgaJpZM4PQGVM&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=H99wJQGgBWkcoainkjvqEarIuUvyd7LMw--mBBb76rw&s=jzqDW_7Ayi9402eZgpLYK2ZqvY6ILZyKa72_xkpVL1Q&e=>.

[zwx168238]

@ncresswell ths but we use harbor ,the default port was 80.but even add the port it still does't work

throw "Failure:invalid reference format""

[deviantony]

@zwx168238 are you using njdocker1.nj.thundersoft.com as the registry URL and public/rsyslog:1.0 as the image you pull ?

[zwx168238]

@deviantony i use njdocker1.nj.thundersoft.com/public/rsyslog:1.0 as the image,it was the full path

[deviantony]

@zwx168238 you need to create a registry first using njdocker1.nj.thundersoft.com and then select that registry when creating a container / pulling an image and use public/rsyslog:1.0 as the image name.

[zwx168238]

@deviantony actually i was do like this

[deviantony]

@zwx168238 and this is not working? Feel free to ping me on Slack to discuss this.

[zwx168238]

@deviantony ths for you hard work , now it was works