After stoping and starting the colima vm cluster is lost when using `vz`

pmalek commented 1 year ago

Description

While using vz I've noticed that when I stop and start the machine the cluster is lost.

The cluster is preserved when I drop --vm-type vz.

Version

Colima Version:

colima version 0.5.1
git commit: fc2ffc3175aa073ba724eb491ec851a154b894da

Lima Version:

limactl version HEAD-585d6e2

Qemu Version:

qemu-img version 7.2.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers

Operating System

[ ] macOS Intel <= 12 (Monterrey)
[ ] macOS Intel >= 13 (Ventura)
[ ] macOS M1 <= 12 (Monterrey)
[X] macOS M1 >= 13 (Ventura)
[ ] Linux

Virtualization type

[X] vz (only macOS Ventura and higher)
[ ] qemu

Mount type

[ ] sshfs
[ ] 9p
[ ] virtiofs

Reproduction Steps

Create a machine

colima start --vm-type vz --network-address --cpu 6 --memory 8 --arch aarch64

Have access to cluster (kubectl get nodes etc) 1.colima stop 1.colima start
Don't have access to cluster, docker ps (from colima machine) gives an empty list

Expected behaviour

After stoping and starting the machine the cluster is preserved

Additional context

No response

abiosoft commented 1 year ago

Do you mean you change VM type of an existing instance to vz? You are actually not supposed to toggle the VM type of an existing instance.

pmalek commented 1 year ago

Do you mean you change VM type of an existing instance to vz? You are actually not supposed to toggle the VM type of an existing instance.

Sorry for not being clear on this. I meant when I change this during creation. I'm not changing for an existing instance.

dekke046 commented 1 year ago

Since the last big upgrade of Colima I experience the same. After OS restart starting Colima al is gone, docker ps-a is empty, the created volumes are also gone. Using Macbook Pro (AMD) and Qemu.

% colima start --network-address  --cpu 6 --memory 8 --disk 100
% docker volume create oracle
% colima stop
% colima start
% docker volume ls
DRIVER    VOLUME NAME

It seems the environment does not persist, even the profile is still there. This behavior was not there in the past.

% colima version
colima version 0.4.6
git commit: 10377f3a20c2b0f7196ad5944264b69f048a3d40

runtime: docker
arch: x86_64
client: v20.10.21
server: v20.10.18

mostafa6765 commented 8 months ago

colima start --vm-type vz --network-address --cpu 6 --memory 8 --arch aarch64

@pmalek and @dekke046 any update on this, i am facing an issue when shutdown my pc then run again previous all containers are empty/gone

abiosoft / colima