@aparcar @7Ji One of our recent changes in the image.mk upstream (https://github.com/openwrt/openwrt/commits/main/include/image.mk) is now generating two files that match the wildcard at https://github.com/openwrt/docker/blob/main/.github/workflows/containers.yml#L474, resulting in failures like this https://github.com/openwrt/docker/actions/runs/26712024650/job/78729065244#step:9:381 https://mirror-03.infra.openwrt.org/snapshots/targets/x86/64/ now has both of these that are matching. The first one is "new", i.e., it only appears since the image.mk file changes. ``` openwrt-x86-64-generic-targz-rootfs.tar.gz openwrt-x86-64-rootfs.tar.gz ```
@aparcar @7Ji
One of our recent changes in the image.mk upstream (https://github.com/openwrt/openwrt/commits/main/include/image.mk) is now generating two files that match the wildcard at https://github.com/openwrt/docker/blob/main/.github/workflows/containers.yml#L474, resulting in failures like this https://github.com/openwrt/docker/actions/runs/26712024650/job/78729065244#step:9:381
https://mirror-03.infra.openwrt.org/snapshots/targets/x86/64/ now has both of these that are matching. The first one is "new", i.e., it only appears since the image.mk file changes.