- [X] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [X] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [X] Have you successfully run `make lint`? - [X] Have you successfully run `pytest tests/unit`? ----- ## Issue A spread test on core18 started [consistently failing](https://github.com/snapcore/snapcraft/actions/runs/3329677836/jobs/5510607616) today. The error is: ``` + sudo -iu ubuntu env -i PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin bash -c 'cd /snapcraft/tests/spread/plugins/v2/snaps/make-hello && snapcraft try --use-lxd' Launching a container. Waiting for container to be ready Waiting for network to be ready... error: cannot communicate with server: Put http://localhost/v2/snaps/system/conf: dial unix /run/snapd.socket: connect: no such file or directory Starting Snapcraft 7.2.1.post6+git822e6686 Logging execution to '/home/ubuntu/.cache/snapcraft/log/snapcraft-20221026-173239.952534.log' An error occurred when trying to execute 'snap unset system proxy.http' with 'LXD': returned exit code 1. ``` I'm not sure why the snapd socket isn't open. I wonder if it's due to an update to snapd. Snapcraft_legacy injects a copy of snapd from the host into the container. It's currently injecting snapd v`2.57.5`. I'm not sure why it's failing only on this particular spread test that calls `snapcraft try`. ## Solution I copied the [snapd setup code](https://github.com/canonical/craft-providers/blob/ab325f27215ae669e6a9f41c507fa79a28f33b19/craft_providers/bases/buildd.py#L695) from `craft-providers`, which appears to solve the problem. (Although a `sleep()` function fixes the error too, the `craft-providers` code is a safer solution)