COmanage Developers List

[Scott Koranda <>]

> > You should make sure you have done a 'git pull' and are creating
> > images/containers that are current.
> 
> Is there a docker-compose command/script that makes creating current
> images/containers easier ?
> 

Hi,

Depending on your specific needs, you should be able to do something
like this:

git pull
export COMANAGE_REGISTRY_VERSION=hotfix-2.0.x
pushd comanage-registry-basic-auth
sed -e s/%%COMANAGE_REGISTRY_VERSION%%/${COMANAGE_REGISTRY_VERSION}/g 
Dockerfile.template  > Dockerfile
docker build -t comanage-registry:${COMANAGE_REGISTRY_VERSION}-basic-auth .
popd

That will build your image using the latest version of the Dockerfile
template and entry point script and using the hotfix-2.0.x branch of the
COmanage Registry GitHub repository. You can then just your existing
compose file to start the suite of services.

Those instructions are on the page at

https://github.com/Internet2/comanage-registry-docker

Now that the Docker templates have stabilized, we can consider an
automated process that runs nightly to create images and pushes them to
DockerHub. We would create an image for each flavor of Docker template
(no auth, basic auth, Shibboleth SP, mod_auth_oidc, slapd, postgres) and
for the COmanage images we would create an image for 

- the current release
- the current hotfix branch, if any
- develop
- other feature branches as deemed useful

I do that now by hand to exercise the pipeline whenever I need a new
image. The images are pushed to DockerHub. I pull from there myself for
some other projects but right now I am the only person doing that.

Please let me know if you have any questions or concerns.

Thanks,

Scott

P.S. I am probably going to add a Docker template that would be based on
the basic-auth template but that would add DebugKit and set 'debug' to
'2' in core.php, to make it easier to spin up a development environment.