Stderr output

<core_client_version>8.2.8</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
docker_wrapper 18 starting
docker_wrapper config:
   workdir: /boinc_slot_dir
   use GPU: no
   Web graphics guest port: 80
   create args: --cap-add=SYS_ADMIN --device /dev/fuse -v /cvmfs:/cvmfs:shared
   verbose: 1
Using Docker
running docker command: ps --all --filter "name=^boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0$" --format "{{.Names}}|{{.Status}}"
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
creating container boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0
running docker command: images
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
building image
running docker command: build "." -t boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709 -f Dockerfile 
program: docker
INFORMATION: This version of Docker has been patched by SUSE.
        These patches allow for automatic access to the host SUSE subscription
        inside containers, allowing for customers to create derived images with
        "docker build" using SUSE packages. However, this feature is
        incompatible with BuildKit and so "docker build" will use the legacy
        builder by default. In order to disable this message and continue using
        the legacy builder, set the DOCKER_BUILDKIT=0 environment-variable.

        In order to opt-in to using BuildKit, set the DOCKER_BUILDKIT=1
        environment-variable. See the SUSE Linux Enterprise Server 15
        documentation for information on how to switch to BuildKit while still
        maintaining access to SCC credentials. In order to use BuildKit, you
        must have the docker-buildx package installed.

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
web graphics: host port 59251, guest port 80
running docker command: create --name boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0  -v "./":"/boinc_slot_dir"  -p 59251:80 --cap-add=SYS_ADMIN --device /dev/fuse -v /cvmfs:/cvmfs:shared boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709
program: docker
docker: unknown server OS: 

Run 'docker create --help' for more information
command output:
starting container
running docker command: start boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: failed to start containers: boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0
command output:
running docker command: ps --all -f "name=boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0"
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
running docker command: logs boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
stderr from container:
stderr end
running docker command: container rm boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709_0
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
running docker command: image rm boinc__lhcathome.cern.ch_lhcathome__theory_2922-4792492-709
program: docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
command output:
2026-03-15 09:12:17 (26889): called boinc_finish(1)

</stderr_txt>
]]>

©2026 CERN