> On Jun 18, 2022, at 18:11, Chris Moore <moore.christopher515(a)gmail.com> wrote:
>
> Hey Mark!
>
> If it makes it easier for the foundation, I can get the host together myself (paying for w/e architecture) and get a proof of concept out for the board to review prior to attaching any kind of DNS record.
Not necessary for you to get the host yourself.
Sorry to have been a little recalcitrant over the last week, but I have just started a new job with <https://status.im> which has been occupying my time.
Erik Hülsmann, a CLF board member, rents <https://hetzner.de/> instances for his CRM company which he essentially donates to the CLF at less than costs, so spinning up a host is no problem.
We have standardized on Debian over Ubuntu as it makes the licensing situation clearer when we need a “special case”. Is there any reason you couldn’t install Discourse in the manner you wish under Debian?
>
> This includes me setting up whatever mail server, getting our daily backups together, and adding necessary plugins (GitHub/Gmail OAuth).
If necessary, we would federate the `USER(a)common-lisp.net` domain. Currently we are running exim as the main MTA due to legacy concerns with mailman2 databases, but we wish to transition to a toplevel `postfix` that will work with the legacy `exim` for the `mailman2` app.
>
> I apologize for trying to rush this - I've got a lot of free time currently due to a lull in work going on at my current company. So I and the dev team are currently not doing much. I want to take advantage of the time while I can.
Cool. Let’s take advantage of it.
>
> Let me know and I'll get this out the door ASAP.
Can you please provide me with the public half of a contemporary-strength SSH keypair. We’ll set up a host, and communicate root@HOST via ip4/6 under separate cover.
yours,
Mark
P.S. if you wanna find me online, let’s figure out a Discord rendezvous. I’m <discord:347061732705042435> aka <discord:easye#8466>.
--
"A screaming comes across the sky. It has happened before but there is nothing
to compare to it now."
When trying to run new CL docker images based on Debian bookworm, I'm
getting errors like this:
```
Executing "step_script" stage of the job script 00:03
Using docker image
sha256:09d35b13e5a86639aa00b12c2f57561e55a6126c78f654df463f3c914e2eff31
for rpgoldman/ccl:latest with digest
rpgoldman/ccl@sha256:746098f1e5c7e82a4f1605817af3137a966b50b7d935caeb5b313f7d20841556
...
shell not found
```
Googling reveals [this gitlab
discussion](https://forum.gitlab.com/t/jobs-fails-shell-not-found-version-p…
following, which suggests a possible work-around, but that also contains
the following note:
> In my case gitlab-runner’s shell detection script was failing to
> stat the available shell executables due to an incompatibility between
> the container and the host, thus returning failure for every check and
> giving up with the “shell not found” error.
> This sometimes happens when running bleeding edge images on older
> hosts, but typically it’s more obvious and often presents itself as
> a filesystem permissions error or some other system call failure.
> Essentially, the binaries/libraries in the container are using
> new/modified system calls that the dockerd/containerd’s seccomp
> layer doesn’t understand yet. *Updating the host kernel and
> container runtime tends to fix this.* [italics added]
Is there any chance that the GitLab host needs a refresh?
Thanks,
R