[GH-ISSUE #36] Simplifications for Docker Compose #3

New issue

Closed

opened 2026-03-04 01:33:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:33:51 +03:00

Owner

Originally created by @rgov on GitHub (Jul 28, 2022).
Original GitHub issue: https://github.com/spr-networks/super/issues/36

The differences between docker-compose-prebuilt.yml and docker-compose-src.yml appear to be whether they specify image or build sections. These could probably be merged (along with run_{prebuilt,docker_compose}.sh) because it is valid to specify both, and the behavior is documented:

Without any explicit user directives, Compose implementation with Build support MUST first try to pull Image, then build from source if image was not found on registry.

The command docker-compose build can explicitly force a build of images locally, and docker-compose pull can explicitly force a pull of all images, which would simplify or obviate the need for pull_containers.sh.

The run_monitor.sh script can apparently be removed, since it references the non-existent file monitor-services-compose.yml.

Originally created by @rgov on GitHub (Jul 28, 2022). Original GitHub issue: https://github.com/spr-networks/super/issues/36 The differences between `docker-compose-prebuilt.yml` and `docker-compose-src.yml` appear to be whether they specify `image` or `build` sections. These could probably be merged (along with `run_{prebuilt,docker_compose}.sh`) because it is valid to specify *both*, and the behavior is documented: > Without any explicit user directives, Compose implementation with Build support MUST first try to pull Image, then build from source if image was not found on registry. The command `docker-compose build` can explicitly force a build of images locally, and `docker-compose pull` can explicitly force a pull of all images, which would simplify or obviate the need for `pull_containers.sh`. The `run_monitor.sh` script can apparently be removed, since it references the non-existent file `monitor-services-compose.yml`.