Issue with deploying new Docker Stack

[soepketel-dev]

When I try to deploy a new Docker Stack, all containers from the packages are in a loop and crash. Below are some examples.

Is this a problem with the packages/repo or is this just me doing something wrong?

legacy-feed-bulk-converter-service

node:internal/modules/cjs/loader:1228
  throw err;
  ^
Error: Cannot find module '/usr/src/app/dist/scripts/legacy-feed-bulk-converter.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Function._load (node:internal/modules/cjs/loader:1055:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

monolith

Node.js v22.14.0
node:internal/modules/cjs/loader:1228
  throw err;
  ^
Error: Cannot find module '/usr/src/app/dist/main.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Function._load (node:internal/modules/cjs/loader:1055:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

schedule-emitter-service

Node.js v22.14.0
node:internal/modules/cjs/loader:1228
  throw err;
  ^
Error: Cannot find module '/usr/src/app/dist/scripts/schedule-emitter.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Function._load (node:internal/modules/cjs/loader:1055:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

[synzen]

Can you try again with the latest builds? I believe this is a flaky issue that might have to do with how nestjs builds files (something that I have not been very satisfied with)

[soepketel-dev]

@synzen I tried again with the latest build, but I'm getting the same result.

Error: Cannot find module.... for all the containers that come from the 5 packages.

Thank you for looking into it.

[synzen]

Apologies for the late response. To be honest, I'm not sure what's happening here - I would figure that having the same images for everybody would prevent these build/run issues from ever happening

Is it possible to provide a step-by-step of what you're doing for me to try to reproduce the issue? The more detailed the steps are, the more accurately I can reproduce what you're doing

[soepketel-dev]

@synzen First of all: I am using Portainer to manage my Docker environment.

I just tried creating the stack on a freshly installed Docker Standalone (Debian 12 Virtual Machine), managed by Portainer (CE). On both CE (Community Edition) and BE (Business Edition) I run into the same result.

1. I create a Fork of the MonitoRSS Repo. I leave the fork network and make the repo private.
2. I add a .env.prod file (with the correct details) to the private Repo.
3. I am creating a new Stack in Portainer. Build method = Repository. I am entering my repo url and credentials (GitHub access token).
4. I click "Deploy the stack". Its now building and installing for a few minutes.

When the containers are created I am getting the errors from the initial Issue message. This exact method is how I used to run MonitoRSS for months. Untill out of a sudden, it did not work anymore.

[synzen]

Thanks for the step-by-step - have you by chance tried without Portainer, to eliminate any possibility of issues related to Portainer?

[mikield]

Can confirm the same on Dokploy.

Also, I think its better to use just .env and not .env.prod.
Because Dokploy for example creates .env file that is editable inside the web panel.