AUTOMATIC1111 web ui fails to start first time

[cococig]

Has this issue been opened before?

• It is not in the FAQ, I checked.
• It is not in the issues, I searched.

Describe the bug

When I run docker compose --profile auto up --build according to the Setup procedure in the Wiki, I get the following error.

...
206.2 Get:384 http://deb.debian.org/debian bullseye/main amd64 publicsuffix all 20220811.1734-0+deb11u1 [127 kB]
206.2 Get:385 http://deb.debian.org/debian bullseye/main amd64 va-driver-all amd64 2.10.0-1 [15.3 kB]
206.3 Get:386 http://deb.debian.org/debian bullseye/main amd64 vdpau-driver-all amd64 1.4-3 [8540 B]
206.3 Get:387 http://deb.debian.org/debian bullseye/main amd64 xauth amd64 1:1.1-1 [40.5 kB]
206.3 Get:388 http://deb.debian.org/debian bullseye/main amd64 xdg-user-dirs amd64 0.17-2 [53.8 kB]
206.3 Fetched 264 MB in 3min 23s (1302 kB/s)
206.3 E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/g/glibc/libc6_2.31-13%2bdeb11u7_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/p/python3.9/libpython3.9-minimal_3.9.2-1_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/p/python3-defaults/libpython3-stdlib_3.9.2-3_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/r/rubberband/librubberband2_1.9.0-1_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/libv/libvidstab/libvidstab1.1_1.1.0-2%2bb1_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/libc/libcdio-paranoia/libcdio-paranoia2_10.2%2b2.0.0-1%2bb2_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/libx/libxcb/libxcb-sync1_1.14-3_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Failed to fetch http://deb.debian.org/debian/pool/main/libd/libdrm/libdrm-radeon1_2.4.104-1_amd64.deb  403  connecting to deb.debian.org:80: connecting to 151.101.110.132:80: dial tcp 151.101.110.132:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [IP: 151.101.110.132 80]
206.3 E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
------
failed to solve: process "/bin/sh -c apt-get update &&   apt-get install -y fonts-dejavu-core rsync git jq moreutils aria2   ffmpeg libglfw3-dev libgles2-mesa-dev pkg-config libcairo2 libcairo2-dev build-essential" did not complete successfully: exit code: 100

This is likely due to an outdated version of Debian used in the base image python:3.10.9-slim, which results in outdated information in /etc/apt/sources.list. To resolve this error, the easiest and least impactful way is to update the base image to the latest version of 3.10.x, which is python:3.10.13-slim.

Which UI

auto

Hardware / Software

• OS: Windows 11 (WSL Ubuntu 20.04.6 LTS)
• OS version: Windows 11 22H2 (Build 22621.2428) / Ubuntu 20.04.6 LTS
• WSL version (if applicable): 2
• Docker Version: 24.0.6
• Docker compose version: v2.22.0-desktop.2
• Repo version: from master
• RAM: 32G
• GPU/VRAM: NVIDIA GeForce RTX 3060 / 12GB

Steps to Reproduce

1. docker compose --profile download up --build
2. docker compose --profile [ui] up --build
3. See error

[CarlosLopezES]

Perfect fix for a real problem :)