Missing a "dot-minikube" personal-files interface to bootstrap a minikube cloud

Bug #2051154 reported by Phan Trung Thanh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Wishlist
Nicolas Vinuesa

Bug Description

Minikube creates its files in $HOME/.minikube, and the ".minikube" part is hard-coded, according to https://minikube.sigs.k8s.io/docs/handbook/config/#exclusive-environment-tunings. as a result, when running `juju clouds` on a machine with minikube installed, juju detects the `.minikube` folder but unable to access it due to it not having access to hidden folders inside $HOME.

A work around that I had to do was to set MINIKUBE_HOME to $HOME/.aws/.minikube which will be much simpler with a "dot-minikube" interface.

- Which juju version this bug was seen in?
Any version of the juju snap with strict confinement (3.1 onwards)
- What cloud the bug was seen on?
Minikube

Revision history for this message
Joseph Phillips (manadart) wrote :

Should be trivial to set this up in our snapcraft.yaml.

Changed in juju:
status: New → Triaged
importance: Undecided → Wishlist
assignee: nobody → Nicolas Vinuesa (nvinuesa)
milestone: none → 3.1.8
Changed in juju:
status: Triaged → In Progress
Revision history for this message
Nicolas Vinuesa (nvinuesa) wrote :
Changed in juju:
status: In Progress → Fix Committed
Revision history for this message
Nicolas Vinuesa (nvinuesa) wrote :
Revision history for this message
Nicolas Vinuesa (nvinuesa) wrote :

Merged PR after the approval from the snapcraft team: https://github.com/juju/juju/pull/17141

Changed in juju:
milestone: 3.1.8 → 3.3.4
Changed in juju:
status: Fix Committed → Fix Released
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.