Use cloud-init to enable lxd-agent on Ubuntu releases before 20.04
#12680
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that `lxd-agent.service` is triggered by `udev` rules and it no longer can be installed as hinted by `systemctl`: ``` The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. LXD agent has been installed, reboot to confirm setup. To start it now, unmount this filesystem and run: systemctl start lxd-agent ``` Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
…buntu images Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
ru-fu
reviewed
Jan 3, 2024
…ling for cloud-init Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
simondeziel
force-pushed
the
cloud-init-instances-without-lxd-agent
branch
from
c426f56
to
0abeb2e
Compare
It is mentioned in a note and a commented out section in the proposed |
ru-fu
reviewed
Jan 3, 2024
simondeziel
force-pushed
the
cloud-init-instances-without-lxd-agent
branch
from
0abeb2e
to
cbef8f0
Compare
…lxd-agent Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
simondeziel
force-pushed
the
cloud-init-instances-without-lxd-agent
branch
from
cbef8f0
to
e650450
Compare
ru-fu
reviewed
Jan 4, 2024
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
simondeziel
force-pushed
the
cloud-init-instances-without-lxd-agent
branch
from
e650450
to
d8d7414
Compare
ru-fu
approved these changes
Jan 4, 2024
tomponline
approved these changes
Jan 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a workaround for the lack of
lxd-agent-loaderpackage in official (ubuntu:andubuntu-daily:) images for releases before20.04.This also document another workaround needed to have
lxd-agentworking on16.04images, namely use the-hwekernel.