I was giving the new actions a spin in https://github.com/canonical/action-build/pull/95, and had trouble building a core20 snap using Snapcraft's 8.x/stable channel. A log of a failed run can be seen here: https://github.com/canonical/action-build/actions/runs/42211786778/job/127871929146 The action was invoked with the following parameters: ``` Run canonical/craft-actions/snapcraft/pack@v1 with: path: ./test-projects/core20 channel: 8.x/stable verbosity: debug test: false env: SNAPCRAFT_IMAGE_INFO: {"build_url": "https://github.com/canonical/action-build/actions/runs/42211786778"} SNAPCRAFT_BUILD_INFO: 1 ``` And the log from the snapcraft invokation is: ``` /usr/bin/sudo --preserve-env --user runner snapcraft pack --verbosity debug 2026-11-06 11:39:23.006 Starting snapcraft, version 8.14.5 2026-11-06 11:39:23.007 Logging execution to '/home/runner/.local/state/snapcraft/log/snapcraft-20261106-113922.989267.log' 2026-11-06 11:39:23.008 lifecycle command: 'pack', arguments: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=True, manifest_image_information='{"build_url": "https://github.com/canonical/action-build/actions/runs/42211786778"}', bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None) 2026-11-06 11:39:23.008 command: pack, arguments: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=True, manifest_image_information='{"build_url": "https://github.com/canonical/action-build/actions/runs/42211786778"}', bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None) Starting snapcraft 8.14.5 from /snap/snapcraft/17614/lib/python3.12/site-packages/snapcraft_legacy/cli. configure_requests_ca: using '/etc/ssl/certs/ca-certificates.crt' for certificate verification snapcraft is running as a snap True, SNAP_NAME set to 'snapcraft' Retrieved snap config: {} snapcraft is running in a docker or podman (OCI) container Parts dir /home/runner/work/action-build/action-build/test-projects/core20/parts Stage dir /home/runner/work/action-build/action-build/test-projects/core20/stage Prime dir /home/runner/work/action-build/action-build/test-projects/core20/prime Set build-for platform to 'amd64' ignoring or passing through unknown parts=OrderedDict({'build': OrderedDict({'plugin': 'meson', 'meson-parameters': ['--prefix=/'], 'source': '.'})}) You need 'multipass' set-up to build snaps: https://multipass.run. ``` So it tried to run with the Multipass backend instead of LXD. The old `snapcore/action-build` would handle this by setting `SNAPCRAFT_BUILD_ENVIRONMENT=lxd` in the environment, which is needed when Snapcraft delegates to the snapcraft_legacy package. If this is added to the new action, it'd be worth keeping in mind the sudo-rs issue described in #147 when deciding how to pass the environment variable to Snapcraft. I imagine the same problem would occur when trying to build core18 snaps with 7.x/stable, but that might be even less of a priority for the new action.