`make run` stdout is very spammy
Categories
(Tecken :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
References
Details
Attachments
(3 files)
Since we adjusted the docker-compose.yaml file to better implement health checks for backing services, when we do make run which does:
docker-compose up web frontend fakesentry
it brings up all the depends_on services as attached. That means we see tons of output from statsd, db, localstack, gcp-emulator, and all their rowdy drunken friends.
In order to be able to see the output from web, fakesentry, and frontend, we need to quell their raucous crosstalk.
| Assignee | ||
Comment 1•2 years ago
|
||
I'm pretty sure we can mark which services are started as detached and that'll fix it. I'm going to try that.
| Assignee | ||
Comment 2•2 years ago
|
||
Comment 3•2 years ago
•
|
||
on docker desktop for mac 4.26.1 i am only being attached to the explicitly listed services web frontend fakesentry
Comment 4•2 years ago
|
||
i am also not being attached to any unspecified services on ubuntu
Comment 5•2 years ago
|
||
what i am getting is lines like this from fakesentry in response to the health check:
fakesentry-1 | [2024-01-30 22:26:47,619] INFO: _internal: 127.0.0.1 - - [30/Jan/2024 22:26:47] "GET / HTTP/1.1" 200 -
but that isn't helped by https://github.com/mozilla-services/tecken/pull/2886
| Assignee | ||
Comment 6•2 years ago
|
||
I've got Ubuntu 23.10 using the docker.io packages:
$ docker version
Client: Docker Engine - Community
Version: 24.0.5
API version: 1.43
Go version: go1.20.6
Git commit: ced0996
Built: Fri Jul 21 20:35:24 2023
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 24.0.5
API version: 1.43 (minimum version 1.12)
Go version: go1.20.6
Git commit: a61e2b4
Built: Fri Jul 21 20:35:24 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.21
GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc:
Version: 1.1.7
GitCommit: v1.1.7-0-g860f061
docker-init:
Version: 0.19.0
GitCommit: de40ad0
It can reproduce the problem regularly:
docker compose stopto shut everything down./slick.shto start backing services and set everything upmake runto run things
Then the backing services are spitting lots of output to stdout.
I looked through the docker compose issue tracker and don't see anything that sounds like this issue. There are some version differences between what Relud has on their Ubuntu setup and what I've got, but nothing that strikes me as fishy. I'm completely stumped as to why I'm having this problem.
I'll adjust fakesentry healthcheck interval to reduce that, too.
| Assignee | ||
Comment 7•2 years ago
|
||
I tried to adjust the fakesentry healtcheck and failed spectacularly. If I adjust the interval to, say, 30s, then it takes 30s before the web service comes up. That stinks.
I wrote up an issue in kent to fix logging. https://github.com/willkg/kent/issues/69
| Assignee | ||
Comment 8•2 years ago
|
||
| Assignee | ||
Comment 9•2 years ago
|
||
| Assignee | ||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
| Assignee | ||
Comment 13•2 years ago
•
|
||
This was deployed just now in bug #1880345 in v2024.02.14. Marking as FIXED.
Description
•