Try HTTP after HTTPS fails (with -f/--force-non-ssl)
MPV opened this issue · 6 comments
Hi,
Does reg support connecting to registries over HTTP (not HTTPS)?
I have a docker registry available only over HTTP, and I haven't yet found a way to get reg to connect to my registry.
Example:
$ docker run \
--rm \
--net=host \
-v $HOME/.docker/daemon.json:/root/.docker/daemon.json:ro \
jess/reg:v0.15.8 \
tags -f my-registry-here/my-image-here
Get https://my-registry-here/my-image-here/v2/: dial tcp my-ip-here:443: connect: connection refused
My $HOME/.docker/daemon.json contains:
{
"insecure-registries" : [
"my-registry-here"
]
}
...compared to docker pull my-registry-here/my-image-here:tag-here that works fine. 😊
have you tried the -f flag :)
Yes, this was using the -f flag.
Sorry for being unclear, I mentioned in the title, and in my example (as tags -f my-registry-here/my-image-here) but I didn't mention it in the description clearly enough. 😊
Seemed to me that the -f flag just stopped when it wasn't successful on HTTPS, instead of (as I had assumed) continuing with trying HTTP after failing with HTTPS — similar to what I suppose is happening with the regular docker client, as I'm able to do it there (when having set the insecure-registries config).
Yes, works with latest. 👍
I couldn't find a newer version tagged on Docker Hub...
https://hub.docker.com/r/jess/reg/tags/
...but I saw that you had released v0.16.0, so I guess it's on its way. 😊
https://github.com/genuinetools/reg/releases/tag/v0.16.0