You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user David Hodgson(jetojedno) wrote on 2021-02-17T08:57:59.096202+00:00
I use some of the devel tools to help creating cloud-init scripts etc for containers. To use just the tools I have to install the whole cloud-init package and then disable all of the installed "active" components so cloud-init doesn't mess with the (desktop) workstation.
Can I request that the devel tools are moved into a separate package so they can be installed without the active parts of cloud-init and, conversly, the installed cloud-init doesn't have unnecessary parts.
The text was updated successfully, but these errors were encountered:
Launchpad user Dan Watkins(oddbloke) wrote on 2021-02-17T14:43:45.501642+00:00
Hi David, thanks for the bug report, this is a good idea!
cloud-init should disable itself in cases where there isn't anything for it to do (like a desktop workstation): have you seen cloud-init run unexpectedly, or have you avoided installing it due to a (very reasonable) abundance of caution? If the former, a separate bug report for that would be great.
Launchpad user David Hodgson(jetojedno) wrote on 2021-02-17T17:21:26.038422+00:00
I immediately mask the cloud* systemd services after install, but I remain a touch concerned as cloud-init runs early in the boot sequence.
I've not seen any unexpected effects, but I boot these workstations rarely, and I haven't been looking for this so wouldn't have necessarily attributed unexpected behaviour to this cause. :-)
This bug was originally filed in Launchpad as LP: #1915901
Launchpad details
Launchpad user David Hodgson(jetojedno) wrote on 2021-02-17T08:57:59.096202+00:00
I use some of the devel tools to help creating cloud-init scripts etc for containers. To use just the tools I have to install the whole cloud-init package and then disable all of the installed "active" components so cloud-init doesn't mess with the (desktop) workstation.
Can I request that the devel tools are moved into a separate package so they can be installed without the active parts of cloud-init and, conversly, the installed cloud-init doesn't have unnecessary parts.
The text was updated successfully, but these errors were encountered: