You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to avoid the question - yes there are certs created by dockerized mkcert on my local-machine:
ls -lah $HOME/.local/share/mkcert
rootCA-key.pem
rootCA.pem
_wildcard.php-stack.docker-key.pem
_wildcard.php-stack.docker.pem
Any suggest? I currently have no live deployment for craneoperator to check ssl works fine there. But I think this should work somehow to if the SSL cert works at all for local development?
I would like to run the registry in https because docker and some other local gitlab-ci begin to suck about non-ssl requests to registry. Hacking my local docker daemon.json to trust insecure-registry is already done, but gitlab-ci runners on my local machine using docker:dind won't have this and that makes everything too confusing.
The text was updated successfully, but these errors were encountered:
Wow... that's funny. I think I've partly resolved my own ticket.
I've tested around and opened a shell in craneoperator docker-container. After running update-ca-certificates immediately the error in web-ui is gone and obviously everything works, at least until the container restarts.
I think it would make sense to run that command in docker-entrypoint or at least give an option to do so if required (or if there are files in '/usr/local/share/ca-certificates/').
I've setup a docker-compose stack with docker registry:v2 and craneoperator. It worked fine with http-only. I've added mkcert local https authority.
I can reach my registry using https://registry-api.php-stack.docker:5000/ (desktop chrome says fine to https-cert).
But craneoperator web-ui tells me:
This is my stack simplyfied:
Just to avoid the question - yes there are certs created by dockerized mkcert on my local-machine:
Any suggest? I currently have no live deployment for craneoperator to check ssl works fine there. But I think this should work somehow to if the SSL cert works at all for local development?
I would like to run the registry in https because docker and some other local gitlab-ci begin to suck about non-ssl requests to registry. Hacking my local docker daemon.json to trust insecure-registry is already done, but gitlab-ci runners on my local machine using docker:dind won't have this and that makes everything too confusing.
The text was updated successfully, but these errors were encountered: