I suppose that is the root cause and what prompted the topic. I am stuck on this Windows machine and started this journey with the Windows installer, which of course was an easy installation experience. However I think I’ve encountered a bug on that which I think needs some further investigation, but wanted to keep moving forward. So I found the container published under the “jujusolutions” org in Docker Hub and that was very quick and easy to get going. But it only went up to 2.7.6, so I thought I could just modify that to pull in the latest version, and that’s when I found that the PPA stopped at 2.7.6 which is likely why the container is at that state now.
The most ideal situation for me is to fix the Windows client. But I presume that will take some time.
Next in line for ideal for me, is the container because I am running Docker for Windows with the WSL2 back-end (Nope, can’t run snap in WSL2 either). But currently it only supports up to 2.7.6 without a viable way to pull the binary or install the Linux client in a container. (This is what I am doing now because I can move forward, but living with the outdated Juju)
The least ideal and not currently an option is running a Vagrant Ubuntu box on my machine and Snap installing Juju. I don’t have enough horse power on this machine to do that .
So I guess my go forward plan is to run 2.7.6 (in container) until the Windows client is fixed and then I can upgrade at that time. However, having the option to run in a container going forward is also valuable and I think should be available as well. In this case it saved me from being totally blocked.