Interesting thank you.

I already published an image of nostr-rs-relay by using its own Dockerfile and it worked without any issue.

The problem I have with nostream is that the docker-compose.yml want to mount volumes to get access to the code. For example, nostream-db and nostream-migrate, because these containers are node:18-alpine3.16 and postgres, they don't have access to the code without volumes.

https://github.com/Cameri/nostream/blob/d1d4cb9e2512e44812f539a5da61db0e97cec266/docker-compose.yml#L127)

Reply to this note

Please Login to reply.

Discussion

Ah, I see. This dockerfile for nostream needs to include the code necessary to run migrations in the image. The container should be able to run the migrations without mounting a volume..

I see they're doing a two stage build, and it's stripping out the necessary migration stuff (or we just don't know the magic command?). I would change it to include the migrations and file an issue with them about it.

Actually, the migration should be running from the nostream image.. not the db image.. does that make sense? The app container just needs a network connection to the db to run a migration, not run on the db image.. (in addition to making sure it doesn't strip the code out of the nostream image).