The snap module, which processes 'snap' configuration [1] currently runs
just about as early as it can run.  The snapd daemon is not available until
cloud_config_modules time frame [2], so use of 'snap' or any provided
commands is not possible before that.

This means that bootcmd cannot use snap provided commands, but runcmd 
or user-scripts ('#!/bin/sh') can.

I'm marking this fix-released, if you disagree, please justify and re-
open.

[1] http://cloudinit.readthedocs.io/en/latest/topics/modules.html#snap
[2] http://cloudinit.readthedocs.io/en/latest/topics/boot.html

** Changed in: cloud-init (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767131

Title:
  Pre-seeded snaps are not necessarily available for use in cloud-init
  user-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1767131/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to