Unable to find network with name or ID asu-build: network not found

Hi, I've set a local ASU instance a few months ago and it's been working fine, but lately (I'd say a few weeks ago) I get this error:

Status:   failed
Progress:   0s total =   0s in queue +   0s in build

Build failed in   0s total =   0s in queue +   0s to build:
ASU server stderr =
Traceback (most recent call last):
  File "/app/.venv/lib/python3.14/site-packages/rq/worker/base.py", line 1522, in perform_job
    return_value = job.perform()
  File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1342, in perform
    self._result = self._execute()
                   ~~~~~~~~~~~~~^^
  File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1402, in _execute
    result = self.func(*self.args, **self.kwargs)
  File "/app/asu/build.py", line 494, in build
    result = _build(build_request, job)
  File "/app/asu/build.py", line 194, in _build
    container = podman.containers.create(
        image,
    ...<8 lines>...
        image_volume_mode="ignore",
    )
  File "/app/.venv/lib/python3.14/site-packages/podman/domain/containers_create.py", line 412, in create
    response.raise_for_status(not_found=ImageNotFound)
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.14/site-packages/podman/api/client.py", line 85, in raise_for_status
    raise APIError(cause, response=self._response, explanation=message)
podman.errors.exceptions.APIError: 500 Server Error: Internal Server Error (unable to find network with name or ID asu-build: network not found)

ERROR: Build failed with status 500 (--version-to 25.12.3 --device ath79/generic:xiaomi_aiot-ac2350:squashfs)
The above errors are often due to the upgrade server lagging behind the
build server, first suggestion is to wait a while and try again.

My setup consists of podman quadlets (I can add them if necessary, although they're basically following the official compose file).

As my setup is currently using rootless pasta networking, I can create the asu-build network, but ASU isn't able to use it.

I don't know if I'm the only one with this issue, because of the quadlet setup instead of podman-compose, but I thought I'd ask to see if there is a workaround. Thanks!

Edit: adding the podman run file I use for testing, before setting up the quadlets:

podman pod create \
 --name asu-pod \
 --publish 8000:8000/tcp \
 --net=pasta:--ipv4-only,-a,10.0.2.100,-n,24,-g,10.0.2.2,--dns-forward,10.0.2.3,-m,1500,--no-ndp,--no-dhcpv6,--no-dhcp \

podman run \
 --detach \
 --label "io.containers.autoupdate=registry" \
 --pod asu-pod \
 --name asu-server \
 --env PUBLIC_PATH=/data/public \
 --env REDIS_URL="redis://asu-redis:6379/0" \
 --env TZ=Europe/Madrid \
 --volume asu.toml:/app/asu.toml:ro \
 --volume asu-data:/public:ro \
 --restart on-failure \
 --memory 500M \
 docker.io/openwrt/asu:latest uv run uvicorn --host 0.0.0.0 --reload --reload-include asu.toml asu.main:app

podman run \
 --detach \
 --label "io.containers.autoupdate=registry" \
 --pod asu-pod \
 --name asu-worker \
 --env PUBLIC_PATH=/data/public \
 --env REDIS_URL="redis://asu-redis:6379/0" \
 --env TZ=Europe/Madrid \
 --volume asu.toml:/app/asu.toml:ro \
 --volume asu-data:/public \
 --volume /run/user/1000/podman/podman.sock:/var/podman.sock:ro \
 --restart on-failure \
 --memory 1G \
 docker.io/openwrt/asu:latest uv run rqworker --logging_level INFO

podman run \
 --detach \
 --label "io.containers.autoupdate=registry" \
 --pod asu-pod \
 --name asu-redis \
 --env TZ=Europe/Madrid \
 --volume asu-redis:/data \
 --restart on-failure \
 --memory 500M \
 docker.io/redis/redis-stack-server

The traceback points to asu/build.py::_build around line 194, where Podman creates the build container; start there and compare its network configuration with the official compose setup. Reproduce the rootless pasta and quadlet setup, then verify that a build no longer fails with the missing asu-build network.