Simple Setup Guide - Error on Compose

[jcap49]

Hi team,

I've followed the instructions in the Simple Setup Guide & see the below error when running the M1-specific script docker-compose -f docker-compose-m1.yml up:

service "pims_remsadmin_mongo" refers to undefined volume pims_remsadmin_mongo: invalid compose project

I've confirmed the Mongo instance is running via the Docker desktop app & not sure what else might be causing this error. Any ideas?

Thank you!

[smalho01]

Hey @jcap49 thanks for bringing this issue to our attention! Turns out we had missed some volume variable names with our production docker configs when we made our last release and there was a mismatch. Since most of the team uses our development environment, this went completely unnoticed. We have since pushed up a hot fix to our main branch and updated the release accordingly.

Please run git pull in the directory where you installed this repository and try running docker-compose -f docker-compose-m1.yml up again and you should be able to get the prototype up and running without any crashes.

Do note that we are in the process of upgrading all of our docker images for better support with M1 macs. In our REMSv0.9 release we only upgraded our keycloak image as that was breaking. There may still be some performance issues with the current install on M1 Macs so be patient when running the prototype. Nothing should crash completely though so long as your machine has allocated enough resources to docker as our internal team has tested this on M1 Macs already. Those performance issues should be addressed in our REMSv0.10 release which will come out in early May.

Let us know if this works for you and if you have any further question or need further support! If not, we will likely close out this issue in a few days. Thanks again for bringing this issue to our attention!

[jcap49]

Amazing - thanks very much for the quick response Sahil. I'll report back on any issues & otherwise, appreciate you looking into this. Best, John

…

On Thu, Apr 6, 2023 at 11:55 AM Sahil Malhotra ***@***.***> wrote: Hey @jcap49 <https://github.com/jcap49> thanks for bringing this issue to our attention! Turns out we had missed some volume variable names with our production docker configs when we made our last release. Since most of the team uses our development environment, this went completely unnoticed. We have since pushed up a hot fix to our main branch and updated the release accordingly. Please run git pull in the directory where you installed this repository and try running docker-compose -f docker-compose-m1.yml up again and you should be able to get the prototype up and running without any crashes. Do note that we are in the process of upgrading all of our docker images for better support with M1 macs. In our REMSv0.9 release we only upgraded our keycloak image as that was breaking. There may still be some performance issues with the current install on M1 Macs so be patient when running the prototype. Nothing should crash completely though so long as your machine has allocated enough resources to docker as our internal team has tested this on M1 Macs already. Those performance issues should be addressed in our REMSv0.10 release which will come out in early May. Let us know if this works for you and if you have any further question or need further support! If not, we will likely close out this issue in a few days. Thanks again for bringing this issue to our attention! — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALEDHTEOYXQG5HYV3BBAE3W737SPANCNFSM6AAAAAAWUUQSDQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- John Capecelatro www.johncapecelatro.com <http://johncapecelatro.com> 315-749-8433

[jcap49]

Quick update - I ran the docker compose command & got the below error message; not sure if this was a result of me not having the Mongo instance running in parallel or if it was another variable reference issue. I'm new to Docker so it's entirely possible this is my fault!

rems_prod_m1_pims                   | Listening on port 5051
rems_prod_m1_pims                   | (node:116) [MONGOOSE] DeprecationWarning: Mongoose: the `strictQuery` option will be switched back to `false` by default in Mongoose 7. Use `mongoose.set('strictQuery', false);` if you want to prepare for this change. Or use `mongoose.set('strictQuery', true);` to suppress this warning.
rems_prod_m1_pims                   | (Use `node --trace-deprecation ...` to show where the warning was created)
rems_prod_m1_crd-request-generator  | [1] ℹ ｢wds｣: Project is running at http://172.18.0.2/
rems_prod_m1_crd-request-generator  | [1] ℹ ｢wds｣: webpack output is served from
rems_prod_m1_crd-request-generator  | [1] ℹ ｢wds｣: Content not from webpack is served from /home/node/app/crd-request-generator/public
rems_prod_m1_crd-request-generator  | [1] ℹ ｢wds｣: 404s will fallback to /
rems_prod_m1_crd-request-generator  | [1] Starting the development server...
rems_prod_m1_crd-request-generator  | [1]
rems_prod_m1_pims                   | MongooseServerSelectionError: getaddrinfo ENOTFOUND pims_remsadmin_mongo
rems_prod_m1_pims                   |     at NativeConnection.Connection.openUri (/home/node/app/pims/node_modules/mongoose/lib/connection.js:825:32)
rems_prod_m1_pims                   |     at /home/node/app/pims/node_modules/mongoose/lib/index.js:411:10
rems_prod_m1_pims                   |     at /home/node/app/pims/node_modules/mongoose/lib/helpers/promiseOrCallback.js:41:5
rems_prod_m1_pims                   |     at new Promise (<anonymous>)
rems_prod_m1_pims                   |     at promiseOrCallback (/home/node/app/pims/node_modules/mongoose/lib/helpers/promiseOrCallback.js:40:10)
rems_prod_m1_pims                   |     at Mongoose._promiseOrCallback (/home/node/app/pims/node_modules/mongoose/lib/index.js:1285:10)
rems_prod_m1_pims                   |     at Mongoose.connect (/home/node/app/pims/node_modules/mongoose/lib/index.js:410:20)
rems_prod_m1_pims                   |     at main (file:///home/node/app/pims/src/backend/server.js:23:18)
rems_prod_m1_pims                   |     at file:///home/node/app/pims/src/backend/server.js:11:1
rems_prod_m1_pims                   |     at ModuleJob.run (internal/modules/esm/module_job.js:183:25) {
rems_prod_m1_pims                   |   reason: TopologyDescription {
rems_prod_m1_pims                   |     type: 'Unknown',
rems_prod_m1_pims                   |     servers: Map(1) { 'pims_remsadmin_mongo:27017' => [ServerDescription] },
rems_prod_m1_pims                   |     stale: false,
rems_prod_m1_pims                   |     compatible: true,
rems_prod_m1_pims                   |     heartbeatFrequencyMS: 10000,
rems_prod_m1_pims                   |     localThresholdMS: 15,
rems_prod_m1_pims                   |     setName: null,
rems_prod_m1_pims                   |     maxElectionId: null,
rems_prod_m1_pims                   |     maxSetVersion: null,
rems_prod_m1_pims                   |     commonWireVersion: 0,
rems_prod_m1_pims                   |     logicalSessionTimeoutMinutes: null
rems_prod_m1_pims                   |   },
rems_prod_m1_pims                   |   code: undefined
rems_prod_m1_pims                   | }
 

[smalho01]

Hey @jcap49, running docker-compose with our configuration will also start up a mongo instance for you. It sounds like you are trying to run and connect with your own instance of mongo, which is possible but would require further manual configuration in the docker-compose-m1.yml file. If you look at the logs for 'rems_prod_m1_pims_remsadmin_mongo', which is not depicted above, it likely shut down and failed because of a port conflict on 27017. You have a few options on how to get around this.

1. The most simplest would be to just shut down your mongo instance and run the docker-compose command again, effectively removing the port conflict with no further modifications.

2. If you want to have your own mongo instance running for another project, change line 65 of docker-compose-m1.yml from '27017:27017' to '27018:27017'. This will run two instances of mongo though, one inside a container from the prototype and one for your own instance, which will take up more resources. By changing the port mappings you should effectively remove the port conflict.

3. Use your own mongo instance with the prototype. To do this change "MONGO_HOSTNAME" under 'pims' (line 78) and 'rems-administrator' (line 59) to be the connection string of your mongo instance. You should also comment out the entire block 'pims_remsadmin_mongo' (lines 61-71) so that docker-compose does not try to create another mongo instance. Quick note, if you are running mongo on your localhost and want the container to connect to your machines localhost, you need to use host.docker.internal as your hostname instead of localhost. See here for more details on docker networking: https://stackoverflow.com/questions/24319662/from-inside-of-a-docker-container-how-do-i-connect-to-the-localhost-of-the-mach

[jcap49]

Thanks very much for the context Sahil. I’ll give this a try and report back with any issues.

On Fri, Apr 7, 2023 at 08:09 Sahil Malhotra ***@***.***> wrote: Hey @jcap49 <https://github.com/jcap49>, running docker-compose with our configuration will also start up a mongo instance for you. It sounds like you are trying to run and connect with your own instance of mongo, which is possible but would require further manual configuration in the docker-compose-m1.yml file. If you look at the logs for 'rems_prod_m1_pims_remsadmin_mongo' which is not depicted above, it likely shut down and failed because of a port conflict on 27017. You have a few options on how to get around this. 1. The most simplest would be to just shut down your mongo instance and run the docker-compose command again, effectively removing the conflict 2. If you want to have your own mongo instance running for another project, change line 65 of docker-compose-m1.yml from '27017:27017' to '27018:27017'. This will run two instances of mongo though, one inside a container from the prototype and one for your own instance. 3. Use your own mongo instance with the prototype. To do this change "MONGO_HOSTNAME" under 'pims' (line 78) and 'rems-administrator' (line 59) to be the connection string of your mongo instance. You should also comment out the entire block 'pims_remsadmin_mongo' (lines 61-71) so that docker-compose does not try to create another mongo instance. Quick note, if you are running mongo on your localhost and want the container to connect to your machines localhost, you need to use host.docker.internal as your hostname instead of localhost. See here for more details on docker networking: https://stackoverflow.com/questions/24319662/from-inside-of-a-docker-container-how-do-i-connect-to-the-localhost-of-the-mach — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALEDHSDJUQJ2PWD6K2NVFTXAANZJANCNFSM6AAAAAAWUUQSDQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- John Capecelatro www.johncapecelatro.com <http://johncapecelatro.com> 315-749-8433

[smalho01]

I'm closing this issue since it hasn't been used in a month. If the problem persists feel free to open this back up again and we'll take a look.