The container no longer works because caddy no longer gets installed. This probably happened during the last build - the image still builds fine, but caddy never gets installed because the caddy build server has been deprecated.

This line fails without halting the build:

Step 5/10 : RUN curl https://getcaddy.com | bash -s personal http.cgi
 ---> Running in e4bca9c12280
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error

Then when the image runs you get:

/app/entrypoint.sh: line 43: caddy: not found

As a workaround you could build off an existing caddy+cgi image. I'll submit a PR as a suggestion.

Launching http-doom in Google Cloud from the README’s ”Launch on Google Cloud Run” provisions multiple cloud run instances.

As a result game is unplayable because there are multiple game instances running on multiple servers against the single client. By default there are multiple servers which return overlapping pixels so everything flickers.

Instance count needs to be manually set to 1 to get only a single game.

Thank you for the software. t: basil hiiri