LAB 4.1 docker compose build fails

seaquest8192

sha256:941a647ff357b9178f9d3d8260ed25d844ff821a22d4dafed9d0af2b3c1ca0af 1.05MB / 61.36MB 271.7s

This gets stuck at 1.05MB - the build never completes no matter how long I wait.

Full output here:

WARN[0000] /home/g.v.rose/devops-repo/setup/docker-compose.yaml: the attribute version is obsolete, it will be ignored, please reove it to avoid potential confusion
[+] Building 316.3s (4/13) [+] Building 316.4s (4/13) [+] Building 316.6s (4/13) [+] Building 316.7s (4/13) [+] Building 316.8s (4/13) [+] Building 316.9s (4/13) [+] Building 327.2s (4/13)
=> [internal] load local bake definitions 0.0ss
=> => reading from stdin 388B 0.0ss
=> [internal] load build definition from Dockerfile 0.0ss
=> => transferring dockerfile: 1.10kB 0.0ss
=> [internal] load metadata for docker.io/jenkins/jenkins:2.452.3-lts-jdk21 1.5ss
=> [internal] load .dockerignore 0.0ss
=> => transferring context: 2B 0.0ss
=> [1/9] FROM docker.io/jenkins/jenkins:2.452.3-lts-jdk21@sha256:51a25fe662aafe0969696e661ca5296041a5d55d4c66bd66d1f63af7 325.5ss
=> => resolve docker.io/jenkins/jenkins:2.452.3-lts-jdk21@sha256:51a25fe662aafe0969696e661ca5296041a5d55d4c66bd66d1f63af78a 0.0ss
=> => sha256:941a647ff357b9178f9d3d8260ed25d844ff821a22d4dafed9d0af2b3c1ca0af 1.05MB / 61.36MB 325.5ss
=> => sha256:51a25fe662aafe0969696e661ca5296041a5d55d4c66bd66d1f63af78a4a6b2b 3.12kB / 3.12kB 0.0ss
=> => sha256:f0f251032519904eab2d3a254804dcdba946388780fba4623cfb235f36cbb9dd 8.85MB / 8.85MB 3.4ss
=> => sha256:828811aa114e45afda2516c42f342e051a6c7db99c77f7a718a9e3640254a7b9 2.58kB / 2.58kB 0.0ss
=> => sha256:1a9715b9dd846a1f9d8666b96fdf492f212ade88b49dcc2e62bb5564084fcefd 12.63kB / 12.63kB 0.0ss
=> => sha256:e9aef93137af6e967e7242f3b3c8ecd8e6f571d1e6fdd9e72db0befeeae3cf13 49.55MB / 49.55MB 11.9ss
=> => sha256:d4c6328162883aab3027931f99aa96b07a981739d217a68f4e4130b0242ded76 1.24kB / 1.24kB 3.6ss
=> => sha256:07b0d8ca8ab78e59d86d891327b173de35ca5b98f150244d7d0ade086a330bcd 184B / 184B 3.8ss
=> => sha256:995009f196ec387953e3a6f67b44dfcf7365e0074eace3faf36a9254630aea55 93.21MB / 93.21MB 11.9ss
=> => extracting sha256:e9aef93137af6e967e7242f3b3c8ecd8e6f571d1e6fdd9e72db0befeeae3cf13 2.0ss
=> => sha256:a559a5c3d54950547150cc5235c054941ff6120844d132711cf53472271cfa61 6.24MB / 6.24MB 12.5ss
=> => sha256:25f6587a42fbde5287f33d61704a652e354efb6f355f2eadd0e02d708df041ef 191B / 191B 12.1ss
=> => sha256:31884c3af3416057b189bcb4ad1779f3e4b8f697db8a12a089972f925dcc5f62 72.29MB / 72.29MB 35.8ss
=> => sha256:0e3f543aa92ecd42788b5b5580f60cee68acb55ae1852394081bc1e6a1a4596f 1.92kB / 1.92kB 12.7ss
=> => sha256:55be5bf73517372e1de54a8ecee4b11532184b4920419c281d7cd1e8d3525a76 1.23kB / 1.23kB 12.9ss
=> => sha256:ff7a2289d5758d28545db89e911bfc46cf4300e12a5912e4140e4245628969ba 392B / 392B 13.0ss

No idea what to do about it. I might try a different version of jenkins when this continues to fail but wonder if that will mess up the rest of the labs.

seaquest8192

Hi,

I ended up getting up and walking away to get some coffee, got into a conversation and then when I got back it had finished after 1057 seconds.

False alarm.

Thanks for the response.

ericegan

Can you give us more information on your setup? Are you on cloud instance?