Closed cdekok closed 6 years ago
I can't reproduce but I'll keep an eye in case I see the same error. We definitely use DNS names, e.g.:
Oh yeah I saw that after only it seems like it is not used because it tries to connect to it's own ip. When i go into the container I do see an env: ARCHIVEMATICA_DASHBOARD_CLIENT_HOST=mysql but it looks like this environment is never used in the code.
➜ am-docker git:(master) ✗ grep -r 'CLIENT_HOST' .
./compose/docker-compose.yml: ARCHIVEMATICA_MCPSERVER_CLIENT_HOST: "mysql"
./compose/docker-compose.yml: ARCHIVEMATICA_MCPCLIENT_CLIENT_HOST: "mysql"
./compose/docker-compose.yml: ARCHIVEMATICA_DASHBOARD_CLIENT_HOST: "mysql"
./src/archivematica/src/MCPClient/install/README.md:- **`ARCHIVEMATICA_MCPCLIENT_CLIENT_HOST`**
./src/archivematica/src/dashboard/install/README.md:- **`ARCHIVEMATICA_DASHBOARD_CLIENT_HOST`**:
./src/archivematica/src/MCPServer/install/README.md:- **`ARCHIVEMATICA_MCPSERVER_CLIENT_HOST`**:
It is definitely used but there is some meta-programming going on that makes it less obvious. See https://github.com/artefactual/archivematica/blob/qa/1.x/src/dashboard/src/settings/base.py#L50-L57 for example.
I can't imagine what could be causing the situation that you're describing. Hopefully you have a chance to debug it and let us know. Thank you!
Sorry the application is loading correctly now I have removed the containers and started over again and it is working now, I probably skipped one of the steps.
I do get another error it seems that it expects webpack to be installed globally but the dashboard did load after restarting the services.
> webpack --progress --colors --entry ./app.js
sh: 1: webpack: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! transfer-browse@0.0.0 prepublish: `webpack --progress --colors --entry ./app.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the transfer-browse@0.0.0 prepublish script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-03-16T10_03_57_466Z-debug.log```
sh: 1: webpack: not found
@ablwr had the same issue but I couldn't reproduce, I'll file a bug.
The archivematica user seems to be missing in the docker-compose file but even if I add it when I go to the application it will complain that it cannot connect.
The configured IP is incorrect
172.28.0.11
instead of172.28.0.5
it would probably be better if it just used the hostnamemysql
what is the best place to configure it?