Timeout at build https://gitlab.senfcall.de:5050

[DavidSchmucker]

At "docker compose build" i get these timeout on "https://gitlab.senfcall.de:5050":

=> CANCELED [alangecker/bbb-docker-nginx:1.21-v4.0.0-v2.5.0 builder 4/6] RUN cd /bbb-learning-dashboard && npm ci && npm run build                             30.3s                                          => CACHED [alangecker/bbb-docker-periodic:v2.5.0-rc.1 stage-0 2/4] COPY --from=library/docker:latest /usr/local/bin/docker /usr/bin/docker                      0.0s
 => CACHED [alangecker/bbb-docker-periodic:v2.5.0-rc.1 stage-0 3/4] COPY bbb-remove-old-recordings bbb-resync-freeswitch entrypoint.sh / 
                        0.0s
 => CACHED [alangecker/bbb-docker-periodic:v2.5.0-rc.1 stage-0 4/4] RUN chmod +x bbb-remove-old-recordings                               
                        0.0s
 => [alangecker/bbb-docker-periodic:v2.5.0-rc.1] exporting to image                                                                      
                        0.0s
 => => exporting layers                                                                                                                  
                        0.0s
 => => writing image sha256:3db0b7720addf9c6165aa28489f0aa9cf89ed19254b1c5a940d054c61b1dc4dd                                             
                        0.0s
 => => naming to docker.io/alangecker/bbb-docker-periodic:v2.5.0-rc.1                                                                    
                        0.0s
------
 > [alangecker/bbb-docker-fsesl-akka:v2.5.0 internal] load metadata for gitlab.senfcall.de:5050/senfcall-public/docker-bbb-build:v2022-03
-30:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to
 do request: Head "https://gitlab.senfcall.de:5050/v2/senfcall-public/docker-bbb-build/manifests/v2022-03-30": dial tcp 159.69.2.199:5050
: i/o timeout

[alangecker]

For me the gitlab.senfcall.de server seems online, maybe it was just a temporary issue on their side? could you try again? :)

[DavidSchmucker]

Ok, you are right! :)