Page MenuHomeDevCentral

Document HTTP/HTTPS pitfall when pulling from the local Docker registry
Needs RevisionPublic

Authored by ptdradmin on Sat, Jul 18, 19:45.
Tags
None
Referenced Files
F37145311: D4131.id10834.diff
Sun, Jul 19, 07:15
F37145308: D4131.id10833.diff
Sun, Jul 19, 07:15
F37134870: D4131.diff
Sun, Jul 19, 06:29
F37025919: image.png
Sat, Jul 18, 21:48
Subscribers
None

Details

Summary

Pulling from localhost:5000 fails with "server gave HTTP response to
HTTPS client" because that endpoint is plain HTTP while Docker expects
HTTPS by default. registry.nasqueron.org is the same registry behind
our HTTPS reverse proxy and works everywhere without extra config, so
recommend it for pulls, including from docker-001.

Refs T1792

Diff Detail

Repository
rINFRAWWW Nasqueron infrastructure servers website
Lint
Lint Passed
Unit
No Test Coverage
Branch
main
Build Status
Buildable 6752
Build 7040: arc lint + arc unit

Event Timeline

ptdradmin created this revision.

Fix: the pull failure was reported on docker-002, not docker-001.

image.png (1×487 px, 126 KB)

Instead of documenting the error in a warning block, I'd suggest we keep a primary callout block with directly the good instructions you wrote.

We could add a very brief explanation why localhost:5000 doesn't work.

Perhaps this?

<div class="callout primary">
    <h3>Pull a container</h3>
    <p>
        Pull with <code>registry.nasqueron.org/image_name</code>.
    </p>
    <p>
        Always use <code>registry.nasqueron.org</code> as Docker pulls by default in HTTPS.
        If you try to pull from `localhost:5000`, you won't get a certificate.
    </p>
</div>

Follow-up change

In another commit / differential, it could be a good idea to increase the column width, so we avoid the débordemnent of the monospaced text in both Add a container and Pull a container section.

dereckson requested changes to this revision.Sat, Jul 18, 21:48
This revision now requires changes to proceed.Sat, Jul 18, 21:48