AM-Labs Docker failing

[Charles Dixon]

Hi,

We're investigating the use of Docker to facilitate deployment of Archivematica (at least into testing environments). I've found the Docker Compose scripts in the labs am repository. I have the build up command working but the make bootstrap is failing during the bootstrap-docker-db step. The error that I'm seeing is 

archivematica.common:storageService:create_pipeline:113:  Unable to create Archivematica pipeline in storage service from {'api_key': u'test', 'uuid': u'183afaf7-bf16-4919-85a4-9f45002e4acc', 'shared_path': '/var/archivematica/sharedDirectory/', 'api_username': u'test', 'create_default_locations': True, 'description': 'Archivematica on 5111a71d698d'} because 503 Server Error: Service Unavailable for url: http://archivematica-storage-service:8000/api/v2/pipeline/

Looking at the `docker ps` output it appears that the storage container is running and exposing port 8000. Is anyone able to suggest anything that I can look into for this?

Thanks,

Charles

[Jesús García Crespo]

Hi Charles,

Are all the services up? If you run `docker-compose ps` you should see the list of services and its state. If some services are down make sure they're started. I would do that with:

$ docker-compose up -d --build
$ make bootstrap
$ make restart-am-services

See also https://github.com/artefactual-labs/am/tree/master/compose#installation.

--
You received this message because you are subscribed to the Google Groups "Archivematica Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematica-tech+unsubscribe@googlegroups.com.
To post to this group, send email to archivematica-tech@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica-tech/b80fce29-dea2-4105-a4c2-f05292438017%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jesús García Crespo,
Software Developer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

[Charles Dixon]

Hi,

Thanks for replying, I had meant to update this. The issue has been related to us having a HTTP proxy. I've got around this by forking the am and Archivematica repositories and updating the submodule within am to point to our fork of Archivematica. I've also updated the docker-compose.yml to add proxy settings to build.args for each of the images (and no_proxy so that the containers can see each other). I've updated the dashboard dockerfile within Archivematica to add

RUN su -l archivematica -c "npm config set proxy $HTTP_PROXY && npm config set https-proxy $HTTPS_PROXY"
RUN su -l archivematica -c "git config --global http.proxy $HTTP_PROXY && git config --global https.proxy $HTTPS_PROXY"

So that git and npm also know about the proxy as they don't use the environment variables.

Charles