You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 28, 2021. It is now read-only.
In running jx v3, on a minikube instance, it seems `Taking snapshot of files..." takes a very long time. Nothing seems to change or move, and looking at the logs you almost worry it's broken.
that sounds like its a container build. Building images on minikube is pretty slow in general; since it has to download all of the layers for all of the images it needs to build the new images; then push them all back up to somewhere (e.g. github's container registry). So generally speaking, initial pipelines can take a very long time on minikube.
There's nothing I'm aware of to give an indication in minikube as to progress of a container build.
Maybe put some notes about it in the documentation? For a first time user it's close to that "Oh crap is something broken?" time of length. Some heads up would be nice :)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
In running
jx
v3, on a minikube instance, it seems `Taking snapshot of files..." takes a very long time. Nothing seems to change or move, and looking at the logs you almost worry it's broken.It hangs for "10-12" mins, https://youtu.be/Id2bj-xQQ5w is an example of me seeing this real time.
Is there a way to get more information on the status, or is it something to do with minikube and the resources it has?
The text was updated successfully, but these errors were encountered: