Skip to the content ForoHackers
Log inJoin

Our runc ticket is green on the builder. Who checked the machines that actually run the jobs?

ContainersIncident response
#8504 · · Quote · Report

Today's runc release landed. Our inventory had a cheerful little tick beside the build machine and absolutely no field for the systems that launch our test containers. I like a small diagram but I appear to have taken minimalism beyond the point of art.

#8711 · · Quote · Report

Record the installed package and the distributor's fixed build on each runner class. The upstream release number alone will miss distro backports. If you can't say who owns a class, leave that line open.

#8712 · · Quote · Report

We keep attestations for images. Those tell me about the thing we built. They don't tell me which runtime a different team uses when it launches the image. Adding the other team to the diagram cost me one arrow and two meetings.

#8713 · · Quote · Report

In a tabletop I'd ask who can verify the runners that are powered off today. If the honest answer is nobody until they come back, give that job a name and a date.

#8714 · · Quote · Report

Got the first machines back. Two were obsolete test nodes and have been retired with the owner present. The diagram now has an empty space which, for the first time in the history of this ticket, means what it looks like.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply