[Debian-salsa-ci] Insights into custom Salca CI "Cannot connect to the Docker daemon” error

[Soren Stoutner]

To handle qt6-webengine, which produces artifacts too large to be uploaded 
with the current 750 MB constraint, I need to setup a custom Salsa CI.

https://salsa.debian.org/soren/qt-6-webengine-salsa-ci/-/blob/salsa/debian/
salsa-ci.yml?ref_type=heads

So far, I have been able to get lintian, blhc, autopkgtest, and debrebuild to 
work.  But I receive an odd error with piuparts.

docker: Cannot connect to the Docker daemon at tcp://docker:2375. Is the 
docker daemon running?.

https://salsa.debian.org/soren/qt-6-webengine-salsa-ci/-/jobs/8818813#L36

Because these tests take longer than the standard runners allow, I am using a 
custom runners on my own server.  They don’t have problems with piuparts using 
the default Salsa CI, so I assume this is some misconfiguration/typo in my 
modified salsa-ci.yml.

Does anyone have any hints that could point me in the right direction for 
figuring out why piuparts can’t communicate with the Docker daemon?

-- 
Soren Stoutner
soren at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/debian-salsa-ci/attachments/20260114/7fb9814e/attachment-0001.sig>