I have investigated the code and confirmed that apt commands are disabled if lxc-clone = true.
It appears this change was done back in January before 1.18 shipped.
Juju 1.20 ships with lxc-clone true by default, whereas earlier versions had it turned off. The way to restore previous behaviour is to simply to configure locally deployed environments with lxc-clone=false in environments.yaml.
The reason lxc-clone is now true is because of requests from the MAAS guys and customers to make local provider faster.
There's work in progress to allow apt-get upgrade to be optional. As part of that work, I think we should revisit the decision to turn off apt commands when cloning.
I'm taking this bug off 1.20 since there's an easy way to restore the older behaviour, and we have a broader fix coming for 1.21. If there are concerns with that, let me know.
I have investigated the code and confirmed that apt commands are disabled if lxc-clone = true.
It appears this change was done back in January before 1.18 shipped.
Juju 1.20 ships with lxc-clone true by default, whereas earlier versions had it turned off. The way to restore previous behaviour is to simply to configure locally deployed environments with lxc-clone=false in environments.yaml.
The reason lxc-clone is now true is because of requests from the MAAS guys and customers to make local provider faster.
There's work in progress to allow apt-get upgrade to be optional. As part of that work, I think we should revisit the decision to turn off apt commands when cloning.
I'm taking this bug off 1.20 since there's an easy way to restore the older behaviour, and we have a broader fix coming for 1.21. If there are concerns with that, let me know.