local lxd provider always use the unix socket
Bug #1664721 reported by
Adam Stokes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
Im running into this issue when both deb package lxd and snap package lxd are installed side by side.
Since Juju only uses the unix socket for bootstrap and I think the https port for state server you either get a collision or juju end up picking the wrong LXD.
I believe I understand why we do it this way for handling remote lxd setups, however, for a local lxd deployment it would be really nice to always just use the unix socket and then I could control which lxd juju uses by altering LXD_DIR.
tags: | added: conjure |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
milestone: | 2.1.1 → 2.1.0 |
milestone: | 2.1.0 → 2.1-rc2 |
To post a comment you must log in.
Just an additional note, having this feature is a huge benefit for giving me the ability to better control the stability of conjure-up by making sure all moving parts are versioned the same as what is run through our CI. Building a snap with everything I need relieves a huge unknown about whether LXD version X is going to work with conjure-up version Y.
A quick win here would be to allow a user to define which LXD api port Juju should connect to since the bootstrap portion already honors the LXD_DIR setting.