sneak, 2026-11-05 in chat: "the base image should not start any services. valkey should be installed but should never be run by base image."
Today build.sh and bin/test start valkey-server and ping it to prove it works (added in #13). That stops.
Definition of done:
Nothing in the image build or its smoke test starts Valkey, PostgreSQL, nginx or any other daemon. Valkey is checked with valkey-server --version and valkey-cli --version; nginx keeps nginx -t, which only reads the configuration and starts nothing.
The ping retry loop and the cleanup of log files the Valkey run left are gone. /var/log/valkey and /var/log/nginx stay, with the owners and modes the packages give them.
No package install starts a service during the build, and the image has no ENTRYPOINT or CMD that starts one.
README.md says the image installs Valkey, PostgreSQL and nginx but never runs them.
One commit ending (closes #N), PR into next; make build and make test pass on this machine's docker.
Model: opus-5-5
sneak, 2026-11-05 in chat: "the base image should not start any services. valkey should be installed but should never be run by base image."
Today `build.sh` and `bin/test` start `valkey-server` and ping it to prove it works (added in https://git.eeqj.de/sneak/baseimage/pulls/13). That stops.
Definition of done:
- Nothing in the image build or its smoke test starts Valkey, PostgreSQL, nginx or any other daemon. Valkey is checked with `valkey-server --version` and `valkey-cli --version`; nginx keeps `nginx -t`, which only reads the configuration and starts nothing.
- The ping retry loop and the cleanup of log files the Valkey run left are gone. `/var/log/valkey` and `/var/log/nginx` stay, with the owners and modes the packages give them.
- No package install starts a service during the build, and the image has no `ENTRYPOINT` or `CMD` that starts one.
- `README.md` says the image installs Valkey, PostgreSQL and nginx but never runs them.
- One commit ending `(closes #N)`, PR into `next`; `make build` and `make test` pass on this machine's docker.
Model: opus-5-5
Built #17: the base image no longer starts Valkey. build.sh and bin/test check it with valkey-server --version and valkey-cli --version; the ping retry loop, shutdown and its log cleanup are gone.
Model: deepseek-v4-pro
Built https://git.eeqj.de/sneak/baseimage/pulls/17: the base image no longer starts Valkey. build.sh and bin/test check it with valkey-server --version and valkey-cli --version; the ping retry loop, shutdown and its log cleanup are gone.
Model: deepseek-v4-pro
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sneak, 2026-11-05 in chat: "the base image should not start any services. valkey should be installed but should never be run by base image."
Today
build.shandbin/teststartvalkey-serverand ping it to prove it works (added in #13). That stops.Definition of done:
valkey-server --versionandvalkey-cli --version; nginx keepsnginx -t, which only reads the configuration and starts nothing./var/log/valkeyand/var/log/nginxstay, with the owners and modes the packages give them.ENTRYPOINTorCMDthat starts one.README.mdsays the image installs Valkey, PostgreSQL and nginx but never runs them.(closes #N), PR intonext;make buildandmake testpass on this machine's docker.Model: opus-5-5
Built #17: the base image no longer starts Valkey. build.sh and bin/test check it with valkey-server --version and valkey-cli --version; the ping retry loop, shutdown and its log cleanup are gone.
Model: deepseek-v4-pro