404 when running dcm4chee-arc-light with docker

[Bartłomiej Kruczyk]

Hi, I'm trying to run dcm4chee with docker.

I'm using docker-compose with following docker-compose.yml: https://gist.github.com/bkruczyk/de24ba86d3b13c46accd0e98f4ca684f
All containers are started, but when I'm trying to access http://localhost:8080/dcm4chee-arc/ui I'm getting 404.

What do I do wrong?

[gunterze]

Check /srv/dcm4chee-arc/wildfly/log/server.log for error messages. If there is no such file, check the log of the archive container by

$ docker-compose logs dcm4chee-arc
Attaching to dcm4cheearcpsql_dcm4chee-arc_1
dcm4chee-arc_1   | cp -r /docker-entrypoint.d/configuration /opt/wildfly/standalone
dcm4chee-arc_1   | Added 'admin' to '/opt/wildfly/standalone/configuration/keycloak-add-user.json', restart server to load user
dcm4chee-arc_1   | cp -r /docker-entrypoint.d/deployments /opt/wildfly/standalone
dcm4chee-arc_1   | . /opt/wildfly/standalone/configuration/adjust-dcm4che-realm.sh
dcm4chee-arc_1   | chown -R wildfly:wildfly /opt/wildfly/standalone
dcm4chee-arc_1   | chown -R wildfly:wildfly /storage
dcm4chee-arc_1   | Waiting for ldap:389 ... done
dcm4chee-arc_1   | Waiting for db:5432 ... done
dcm4chee-arc_1   | Waiting for logstash:8514 ... done
dcm4chee-arc_1   | Starting Wildfly 10.1.0.Final
dcm4chee-arc_1   | JAVA_OPTS already set in environment; overriding default settings with values: -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
dcm4chee-arc_1   | =========================================================================
dcm4chee-arc_1   |
dcm4chee-arc_1   |   JBoss Bootstrap Environment
dcm4chee-arc_1   |
dcm4chee-arc_1   |   JBOSS_HOME: /opt/wildfly
dcm4chee-arc_1   |
dcm4chee-arc_1   |   JAVA: /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
dcm4chee-arc_1   |
dcm4chee-arc_1   |   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
dcm4chee-arc_1   |
dcm4chee-arc_1   | =========================================================================
dcm4chee-arc_1   |
dcm4chee-arc_1   | 09:13:32,211 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
dcm4chee-arc_1   | 09:13:32,461 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
dcm4chee-arc_1   | 09:13:32,563 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
dcm4chee-arc_1   | 09:13:33,970 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 28) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/f6/40bf1e28bc6a8c42ba4b06635ad578bdc0ecee/content
dcm4chee-arc_1   | 09:13:33,979 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
dcm4chee-arc_1   | 09:13:33,993 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.4.0.Final
dcm4chee-arc_1   | 09:13:33,998 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.4.0.Final

Would need your docker-compose.env to try to reproduce the problem.

gunter

[Bartłomiej Kruczyk]

Thanks for reply.

Env file here https://gist.github.com/bkruczyk/9824ba524fe8c84420ce697bd65a7df7
Wildfly log here: https://gist.github.com/bkruczyk/847ac9ebf81791fdf3666b6fb3ff433e

I don't know if I'm getting it right, but it seems that there's some problem with LDAP configuration?

[gunterze]

I cannot reproduce the problem on my box (Ubuntu 16.04.1 LTS, Docker version 1.12.3). It starts successfully with your docker-compose.yaml + *.env : https://gist.github.com/gunterze/b5f4bb84eb21c912ec206bb29b7a6da5

[gunterze]

The slapd container log at first startup should like like:

$ docker-compose logs slapd

Attaching to tmp_slapd_1
slapd_1          | invoke-rc.d: policy-rc.d denied execution of stop.
slapd_1          |   Creating initial configuration... done.
slapd_1          |   Creating LDAP directory... done.
slapd_1          | invoke-rc.d: policy-rc.d denied execution of start.
:

slapd_1          | adding new entry "dicomAETitle=DCM4CHEE,cn=Unique AE Titles Registry,cn=DICOM Configuration,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | adding new entry "dicomAETitle=DCM4CHEE_ADMIN,cn=Unique AE Titles Registry,cn=DICOM Configuration,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | adding new entry "dicomAETitle=DCM4CHEE_TRASH,cn=Unique AE Titles Registry,cn=DICOM Configuration,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | SASL/EXTERNAL authentication started
slapd_1          | SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
slapd_1          | SASL SSF: 0
slapd_1          | modifying entry "dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | SASL/EXTERNAL authentication started
slapd_1          | SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
slapd_1          | SASL SSF: 0
slapd_1          | adding new entry "ou=users,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | adding new entry "uid=admin,ou=users,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | adding new entry "uid=user,ou=users,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | adding new entry "cn=admin,ou=users,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | adding new entry "cn=user,ou=users,dc=dcm4che,dc=org"
slapd_1          |
slapd_1          | SASL/EXTERNAL authentication started
slapd_1          | SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
slapd_1          | SASL SSF: 0
slapd_1          | modifying entry "olcDatabase={1}hdb,cn=config"
slapd_1          |
slapd_1          | 582af92f @(#) $OpenLDAP: slapd  (Jan 16 2016 23:00:08) $
slapd_1          |     root@chimera:/tmp/buildd/openldap-2.4.40+dfsg/debian/build/servers/slapd
slapd_1          | 582af92f slapd starting

[Bartłomiej Kruczyk]

Thank you. It turned out that my ldap container didn't add requested entries:

slapd_1 | 582c1438 @(#) $OpenLDAP: slapd (Jan 16 2016 23:00:08) $
slapd_1 | root@chimera:/tmp/buildd/openldap-2.4.40+dfsg/debian/build/servers/slapd
slapd_1 | 582c143a slapd starting

I don't know what was the root issue, but I deleted all containers volumes, updated docker-compose.yml to use version 5.7.2 of dcm4chee-arc and suddenly it all works now :)
Again, thank you for your help.