This version provides docker wrapper v18.

https://lhcathome.cern.ch/lhcathome/result.php?resultid=432618087
First Theory doing docker.
Thank you for updating docker :-)

Proxy is set in default.local, but not used from Task.
Proxy in CentOS9 VM.
init_data.xml select info from proxy:
CVMFS_HTTP_PROXY="http://<10.116.178.201>:<3128>;DIRECT"

tested with and without pattern.

Mine seem OK

Got a proxy from the local environment
Will use it for CVMFS and Frontier
Using CVMFS on the host.
Probing CVMFS repositories ...
Probing /cvmfs/alice.cern.ch... OK
Probing /cvmfs/cvmfs-config.cern.ch... OK
Probing /cvmfs/grid.cern.ch... OK
Probing /cvmfs/sft.cern.ch... OK
Excerpt from "cvmfs_config stat":
VERSION HOST PROXY
2.13.3.0 http://s1cern-cvmfs.openhtc.io http://192.168.1.179:3128
Environment HTTP proxy: http://192.168.1.179:3128

I have without pattern per https://cvmfs.readthedocs.io/en/stable/cpt-configure.html#proxy-lists

curl -I http://example.com
answer is ok.

ChatGPT: podman squid error

ftm: cleaning it in my squid and hoping squid running correct after this.

Don't forget to set proxy in "containers.conf"

Linux podman:
etc/containers/containers.conf

[containers]

env = [
"http_proxy=http://proxy1:3128",
"https_proxy=http://proxy1:3128",
"no_proxy=localhost,127.0.0.0/8,192.168.0.0/16"
]

Impossible to set containers on hold??

Boinc manager says "Task suspended by user"
But I see in runRivet.log that crunching goes on in background.

Boinc manager says "Task suspended by user"
But I see in runRivet.log that crunching goes on in background.

I suppose that it's not in runRivet.log where you see activity, but in stderr.txt.
Only the logging (and checking) of the status of the containers goes on. The container itself is in a paused state, so no real event processing.
I admit that these logging seems much more cpu-intensive than the developers expected.
They decided to to this every 10 seconds probably for interconnection reasons with BOINC.

WOW,
CentOS9 in VM with running squid,
updated System with nearly 400 program updates.

Now Squid showing more infos in this VM.
Seem not the final step, but Docker Tasks running.....

In reply to Crystal Pellet's message of 15 Feb 2026:

I suppose that it's not in runRivet.log where you see activity, but in stderr.txt.

Checked again.
State now is "Waiting to run" because of some Atlas WUs.
But runRivet.log is updating again and again.

From your answer I conclude that it should work. So I need to find the cause.

In reply to Saturn911's message of 15 Feb 2026:

State now is "Waiting to run" because of some Atlas WUs.
But runRivet.log is updating again and again.

From your answer I conclude that it should work. So I need to find the cause.

The difference between your host and mine: Your host runs Linux OS and mine Windows OS.