The cloud-init project has integration tests that run using a variety of user-data configurations and boot LXD containers. One of these tests, checks to make sure cloud-init was setup and running correctly when user-data says to enable snaps.
These tests are current failing and it appears that the 2.26 version of snapd in artful and in proposed is not starting in a lxd. Here is an example using artful:
jenkins@torkoal:/tmp/cloud-init$ lxc launch ubuntu-daily:artful a
Creating a
Starting a
jenkins@torkoal:/tmp/cloud-init$ lxc exec a bash
root@a:~# snap --version
snap 2.26.1+17.10
snapd unavailable
series -
root@a:~# systemctl status snapd
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-05-16 19:08:05 UTC; 38s ago
Process: 447 ExecStart=/usr/lib/snapd/snapd (code=exited, status=201/NICE)
Main PID: 447 (code=exited, status=201/NICE)
CPU: 529us
May 16 19:08:05 a systemd[1]: snapd.service: Failed with result 'exit-code'.
May 16 19:08:05 a systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
May 16 19:08:05 a systemd[1]: Stopped Snappy daemon.
May 16 19:08:05 a systemd[1]: snapd.service: Start request repeated too quickly.
May 16 19:08:05 a systemd[1]: Failed to start Snappy daemon.
May 16 19:08:05 a systemd[1]: snapd.service: Unit entered failed state.
May 16 19:08:05 a systemd[1]: snapd.service: Failed with result 'exit-code'.
Here is another example using the version in zesty, then upgrading to the version in proposed:
jenkins@torkoal:/tmp/cloud-init$ lxc launch ubuntu-daily:z z
Creating z
Starting z
jenkins@torkoal:/tmp/cloud-init$ lxc exec z bash
root@z:~# snap --version
snap 2.24.1+17.04
snapd 2.24.1+17.04
series 16
ubuntu 17.04
kernel 4.4.0-72-generic
After upgrading to the version in proposed:
root@z:~# snap --version
snap 2.26.1+17.04
snapd unavailable
series -
I filed LP: #1690880 to track this as this was working in previous versions and only recently started to fail.