Make lxd.conf used extendable/customisable

Bug #1615876 reported by Anastasia
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Wishlist
Unassigned

Bug Description

From https://github.com/juju/juju/issues/1112:

There are some situations where being able to modify the lxd config used to set up the containers for the local provider could be very handy; please consider providing some way of so doing.

The specific case I'm looking at is the Juju Vagrant images where we want all containers to have an APT proxy set up. The cleanest way to do this would be using lxc hooks to run a script which injects the cache, but we can't do that. As a result, we have to muck around with the templates, which is error-prone, brittle and adds to start-up time (as we have to have all the templates that we want to modify in-place at boot time, meaning we have to download all templates that there might be images for).

Revision history for this message
james beedy (jamesbeedy) wrote :

This should partially Fix Bug #1535891

Revision history for this message
Anastasia (anastasia-macmood) wrote :

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
tags: added: cpe-onsite
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.