SUSE / Portus

Authorization service and frontend for Docker registry (v2)
http://port.us.org/
Apache License 2.0
3k stars 470 forks source link

Using Project JIB to deploy works, but doesn't show up in the UI #2212

Closed dhanishmeht closed 4 years ago

dhanishmeht commented 5 years ago

Description

I am using an SSL enabled Portus installation using the examples directory with clair-SSL. In a Maven project I am using Project JiB to build Docker images and push to the private registry.

When I push via mvn compile jib:build, it shows as successfully pushed to Portus and if I try pulling on another machine, I do get the correct image, which means the registry did get the new pushed image.

If I push via docker push ... command, Portus does show it on the UI

Portus version: 2.4.3@5a616c0ef860567df5700708256f42505cdb995

RjEcho217 commented 5 years ago

How did you get SSL to work on portus? My backend doesnt seem to want to use a Self signed cert nor a CA from our domain controller.... very frustrating.

dhanishmeht commented 5 years ago

I am using the Nginx to handle the SSL, however I am using publicly trusted certificates. I am not sure if Portus verifies certificates and hence the self-signed ones aren't working.

RjEcho217 commented 5 years ago

Yeah our internal network doesnt want to pay for one right now while we test if portus will work for us. Ive placed it everywhere I can find the CA certs should go, to no avail. THe front end website works but the backend keeps failing and registry saying they cannot verify. Just curious, did you simply place it in the secrets folder? Or?

dhanishmeht commented 5 years ago

I will let you know as soon as I get in to work

dhanishmeht commented 5 years ago

I left the actual certificates in the root home directory, and in the secrets folder I do have Portus certificates to work with the backend and also authorize registry but as far as I can remember these are self-signed

stale[bot] commented 4 years ago

Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

dhanishmeht commented 4 years ago

This is not fixed