Steve Shipway
Steve Shipway
This might be caused by different compose parsing under Docker 1.12? I do not have a Docker 1.12 environment to test this under though. The nginx container definitely has the...
@gitlab-pano You could open a shell in the haproxy container, and test to see if 'portus' can resolve (use 'ping portus'). If it can't then this would indicate an issue...
The portus.conf file (for configuring NGINX) is created by the startup.sh script in the Portus container; this is on a shared mount that is subsequently loaded by the proxy container....
I only have the docker-compose and rancher-compose that are in the Rancher Template; this is what we used at the University. https://github.com/rancher/community-catalog/tree/master/templates/registry/2
This version is forked from SUSE/Portus before they added this feature. Therefore, the delete feature will not work until this fork is rolled forwards. I think there may be an...
Fixed in latest commit
I'd like to, but with recent changes in my life I am no longer working with Docker, and so it is difficult to continue to give this project the time...
@livehybrid - did you remember to start the portus container first, and set the `--link portus:portus` on the nginx container to link to it?
The FQDN is supposed to be the FQDN of your registry host (and also the portus host of course). This is used to create a certificate as well as to...
Might be necessary to set up a scheduling affinity rule to get them onto the same host.