Re: cl-docker-images

------=_Part_2412685_1037918048.1764007050491
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Robert,=C2=A0


I did not yet notice your PRs somehow, and with the help of AI, I've been s=
tripping down each cl-docker-images/ project one by one, excising Timmons's=
 legacy matrix-based build pipelines, and replacing with straightforward bu=
ilds on trixie/amd64 only for now. So far I have done this for sbcl/ and cc=
l/. It still uses the ./update.sh to generate a directory per CL impl versi=
on, which contains Dockerfile and support files. And I'm still keeping some=
 (now simplified) shared ci yml code in the cl-docker-images/ci-helpers/=C2=
=A0 project and included in each project's .gitlab-ci.yml, to avoid tedious=
 code repetition in each.=C2=A0

The AI agents have assured me that we can layer back in multi-architecture =
targets in due course, but that Timmons's setup is somewhat over-engineered=
 for our immediate purposes (assuming "immediate purposes" =3D debian on x6=
4/amd64) and is ripe for replacement with more "modern" (and hopefully simp=
ler) alternatives for achieving multi-architectural docker image targets, w=
ith some target platform combos being doable using the local docker on comm=
on-lisp.net without need to depend on a far-flung network of runners set up=
 on physical machines on a rack in a closet at MIT or whereever.=C2=A0

I've already completed a pass of this "stripping down" on sbcl/ and ccl/, s=
o your PR's might not smoothly merge in anymore to those, and I may have to=
 merge them manually unless you'd like to push new commits to your PRs so t=
hey will apply to the current HEAD for sbcl/ and ccl/ (please advise on tha=
t, after reviewing the current sbcl/ and ccl/ HEADs if you will).=C2=A0

I was about to start on ecl or clisp next, but i'll look for your PRs befor=
e starting to rip anything apart on those, perhaps merging before I start r=
ipping those apart and hereby saving myself some work ...=F0=9F=99=8F


Dave

P.S. Since it seems you & I may be looking at some of this stuff concurrent=
ly, feel free to pop into #common-lisp.net on IRC, I'm usually in there as =
dcooper.=C2=A0













---- On Mon, 24 Nov 2025 11:47:50 -0500 Robert Goldman <[email protected]>=
 wrote ---



On 21 Nov 2025, at 18:25, David Cooper wrote:



Hi Dave --

I have bypassed some of these for ASDF.  Originally, I sent pull requests f=
or my updates, but with Eric gone, the PRs were going nowhere, so I dropped=
 that. Instead I started building the docker images by hand, pushing them t=
o my personal DockerHub account, and using those in my GitLab pipelines.

I will check today and make sure there are PRs on GitLab for all of my upda=
ted docker images.  That should help you get started. The configuration tha=
t Eric had is now woefully old -- basing the images on Debian versions that=
 are no longer under LTS.  So you will want those updates.

That said, I was not able to get the windows images to build at all locally=
.  So they may be broken and I haven't updated their base images (at least =
not consistently).

I didn't figure out how to get Eric's toolchain to build the images, either=
. I just used his update.sh script to generate the Dockerfiles and then bui=
lt them myself.  I have no idea how the Gitlab actions are supposed to work=
 with this.

Hope that helps!  More soon when I check the PRs.

R




Hi Robert,

=C2=A0I'm trying to resurrect some of the cl-docker-images pipeline.=C2=A0 =
Just thought I would check with you because I think you have bypassed these=
 for asdf? In case I get them working again I'd like to compare notes and a=
void too much duplication of work, and I'd like to make whatever images I c=
ome up with be compatible for retro-fitting into asdf at some point in case=
 you'd like to relieve yourself of the need to keep your own ones maintaine=
d (or we could adopt your ones as the clnet-hosted ones).

Did you understand all of Timmons's bashbrew runners? I'm replacing those w=
ith a single shell runner on our future host but I'd like to get it to dock=
er-in-docker after that... and maybe support multiarch using emulation (I t=
hink Timmons had actual hardware running each of his platform-specific runn=
ers).=C2=A0

Dave Cooper
------=_Part_2412685_1037918048.1764007050491
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>=
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h=
ead><body ><div style=3D"font-family: Verdana, Arial, Helvetica, sans-serif=
; font-size: 10pt;"><div><br></div><div>Hi Robert,&nbsp;</div><div><br></di=
v><div>I did not yet notice your PRs somehow, and with the help of AI, I've=
 been stripping down each cl-docker-images/ project one by one, excising Ti=
mmons's legacy matrix-based build pipelines, and replacing with straightfor=
ward builds on trixie/amd64 only for now. So far I have done this for sbcl/=
 and ccl/. It still uses the ./update.sh to generate a directory per CL imp=
l version, which contains Dockerfile and support files. And I'm still keepi=
ng some (now simplified) shared ci yml code in the cl-docker-images/ci-help=
ers/&nbsp; project and included in each project's .gitlab-ci.yml, to avoid =
tedious code repetition in each.&nbsp;<br><br>The AI agents have assured me=
 that we can layer back in multi-architecture targets in due course, but th=
at Timmons's setup is somewhat over-engineered for our immediate purposes (=
assuming "immediate purposes" =3D debian on x64/amd64) and is ripe for repl=
acement with more "modern" (and hopefully simpler) alternatives for achievi=
ng multi-architectural docker image targets, with some target platform comb=
os being doable using the local docker on common-lisp.net without need to d=
epend on a far-flung network of runners set up on physical machines on a ra=
ck in a closet at MIT or whereever.&nbsp;<br><br>I've already completed a p=
ass of this "stripping down" on sbcl/ and ccl/, so your PR's might not smoo=
thly merge in anymore to those, and I may have to merge them manually unles=
s you'd like to push new commits to your PRs so they will apply to the curr=
ent HEAD for sbcl/ and ccl/ (please advise on that, after reviewing the cur=
rent sbcl/ and ccl/ HEADs if you will).&nbsp;<br><br>I was about to start o=
n ecl or clisp next, but i'll look for your PRs before starting to rip anyt=
hing apart on those, perhaps merging before I start ripping those apart and=
 hereby saving myself some work ...=F0=9F=99=8F</div><div><br></div><div>Da=
ve<br><br>P.S. Since it seems you &amp; I may be looking at some of this st=
uff concurrently, feel free to pop into #common-lisp.net on IRC, I'm usuall=
y in there as dcooper.&nbsp;</div><div id=3D"Zm-_Id_-Sgn" data-sigid=3D"450=
6931000000010003" data-zbluepencil-ignore=3D"true"><div><br></div><div><br>=
</div><div><br></div></div><div><br></div><div class=3D"zmail_extra_hr" sty=
le=3D"border-top: 1px solid rgb(204, 204, 204); height: 0px; margin-top: 10=
px; margin-bottom: 10px; line-height: 0px;"><br></div><div class=3D"zmail_e=
xtra" data-zbluepencil-ignore=3D"true"><div><br></div><div id=3D"Zm-_Id_-Sg=
n1">---- On Mon, 24 Nov 2025 11:47:50 -0500 <b>Robert Goldman &lt;rpgoldman=
@sift.net&gt;</b> wrote ---<br></div><div><br></div><blockquote id=3D"block=
quote_zmail" style=3D"margin: 0px;"><div><div style=3D"font-family: sans-se=
rif"><div style=3D"white-space: normal" class=3D"x_1559585637markdown"><p d=
ir=3D"auto">On 21 Nov 2025, at 18:25, David Cooper wrote:<br></p><div id=3D=
"zmail_block"><br></div><p dir=3D"auto">Hi Dave --<br></p><p dir=3D"auto">I=
 have bypassed some of these for ASDF.  Originally, I sent pull requests fo=
r my updates, but with Eric gone, the PRs were going nowhere, so I dropped =
that. Instead I started building the docker images by hand, pushing them to=
 my personal DockerHub account, and using those in my GitLab pipelines.<br>=
</p><p dir=3D"auto">I will check today and make sure there are PRs on GitLa=
b for all of my updated docker images.  That should help you get started. T=
he configuration that Eric had is now woefully old -- basing the images on =
Debian versions that are no longer under LTS.  So you will want those updat=
es.<br></p><p dir=3D"auto">That said, I was not able to get the windows ima=
ges to build at all locally.  So they may be broken and I haven't updated t=
heir base images (at least not consistently).<br></p><p dir=3D"auto">I didn=
't figure out how to get Eric's toolchain to build the images, either. I ju=
st used his <code style=3D"margin: 0 0; padding: 0 0.25em; border-radius: 3=
px; background-color: rgb(247, 247, 247)">update.sh</code> script to genera=
te the Dockerfiles and then built them myself.  I have no idea how the Gitl=
ab actions are supposed to work with this.<br></p><p dir=3D"auto">Hope that=
 helps!  More soon when I check the PRs.<br></p><p dir=3D"auto">R<br></p></=
div></div></div><blockquote style=3D"margin: 0 0 5px; padding-left: 5px; bo=
rder-left: 2px solid rgb(119, 119, 119); color: rgb(119, 119, 119)"><p dir=
=3D"auto">Hi Robert,<br></p><p dir=3D"auto">&nbsp;I'm trying to resurrect s=
ome of the cl-docker-images pipeline.&nbsp; Just thought I would check with=
 you because I think you have bypassed these for asdf? In case I get them w=
orking again I'd like to compare notes and avoid too much duplication of wo=
rk, and I'd like to make whatever images I come up with be compatible for r=
etro-fitting into asdf at some point in case you'd like to relieve yourself=
 of the need to keep your own ones maintained (or we could adopt your ones =
as the clnet-hosted ones).<br></p><p dir=3D"auto">Did you understand all of=
 Timmons's bashbrew runners? I'm replacing those with a single shell runner=
 on our future host but I'd like to get it to docker-in-docker after that..=
. and maybe support multiarch using emulation (I think Timmons had actual h=
ardware running each of his platform-specific runners).&nbsp;<br></p><p dir=
=3D"auto">Dave Cooper<br></p></blockquote></blockquote></div><div><br></div=
></div><br></body></html>
------=_Part_2412685_1037918048.1764007050491--