Enable Moby on Ubuntu 26.04 (Resolute)

[Copilot]

Microsoft now publishes Moby packages for Ubuntu 26.04 (resolute) — moby-cli, moby-engine, moby-containerd, moby-buildx — but docker-in-docker and docker-outside-of-docker still hard-blocked resolute when moby: true. Debian trixie remains without Moby packages upstream and stays blocked.

Verified against packages.microsoft.com:

• microsoft-ubuntu-resolute-prod: moby-cli, moby-engine, moby-containerd, moby-buildx, moby-compose, moby-runc, moby-tini present.
• microsoft-debian-trixie-prod: no moby-* packages.

Changes

• src/docker-in-docker/install.sh / src/docker-outside-of-docker/install.sh
  • Added resolute to DOCKER_MOBY_ARCHIVE_VERSION_CODENAMES.
  • Narrowed the pre-install guard to block only Debian trixie (dropped resolute). Existing microsoft-ubuntu-resolute-prod repo setup and the iptables-nft fallback for resolute already cover install/runtime.
• Tests — new install_moby_on_ubuntu_resolute scenarios (moby: true on ubuntu:resolute) + scripts for both features, asserting docker, docker buildx, and installed moby-cli/moby-engine.
• Docs — NOTES.md for both features updated to reflect Moby support on Ubuntu 26.04.

Guard behavior after change:

resolute + moby=true  → proceed (Microsoft repo)
trixie   + moby=true  → blocked (no upstream packages)
noble    + moby=true  → unchanged

• Fixes Enable Moby on Ubuntu 26.04 (Resolute) #1737

[Kaniska (v-Kaniska244)]

Copilot Place the new ubuntu resolute related tests on top in the scenarios.json. Also remove all debian bullseye(11) tests cases from scenarios.json. Patch level bump of both features also required.

[Copilot]

Copilot Place the new ubuntu resolute related tests on top in the scenarios.json. Also remove all debian bullseye(11) tests cases from scenarios.json. Patch level bump of both features also required.

Done. Moved the Ubuntu resolute scenarios to the top of both scenarios.json files, removed all Debian bullseye (11) test cases (the javascript-node:0-18-based scenarios), and bumped patch versions (docker-in-docker → 4.1.1, docker-outside-of-docker → 1.10.1).

[Kaniska (v-Kaniska244)]

Copilot Instead of removing tests with mcr.microsoft.com/devcontainers/javascript-node:0-18 base images, please replace the base images for those with mcr.microsoft.com/devcontainers/javascript-node:3-22

[Copilot]

Copilot Instead of removing tests with mcr.microsoft.com/devcontainers/javascript-node:0-18 base images, please replace the base images for those with `mcr.microsoft.com/devcontainers/javascript-no...

Restored the previously-removed scenarios and updated their base image from javascript-node:0-18 to mcr.microsoft.com/devcontainers/javascript-node:3-22 in both scenarios.json files.

[Kaniska (v-Kaniska244)]

Copilot For docker_build_older test scenario in docker-in-docker, update the version to 23 from 20 and also update the test script accordingly if required

[Copilot]

Copilot For docker_build_older test scenario in docker-in-docker, update the version to 23 from 20 and also update the test script accordingly if required

Updated the docker_build_older scenario's version from 20 to 23. The test script (docker_build_older.sh) only checks generic buildx/build/ps behavior and doesn't assert a specific version, so no script change was needed.