Cannot reset Kubernetes cluster after upgrading to 1.8

FabianKramm commented 2 weeks ago

Describe the bug

When trying to reset the in-built Kubernetes cluster (via Settings...-> Kubernetes -> Reset Cluster) I get the following error message:

unmount nfs: unmount /nfs/for-machines/ro/docker/volumes/126cbb66e0971496382bcd98966f5e8bb759c08e5a012cd94c771246cd4ea9a1: remove /nfs/for-machines/rw/docker/volumes/126cbb66e0971496382bcd98966f5e8bb759c08e5a012cd94c771246cd4ea9a1: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/165c15a985fdec4e1f1a35e92716f2e59b79250cf8c20b7df40ac1a0e98b2f17: remove /nfs/for-machines/rw/docker/volumes/165c15a985fdec4e1f1a35e92716f2e59b79250cf8c20b7df40ac1a0e98b2f17: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/a04d7a2ffb0e156cc1e255437e5f5ea62b9bccaf8e2a91f5f89589e91450358a: remove /nfs/for-machines/rw/docker/volumes/a04d7a2ffb0e156cc1e255437e5f5ea62b9bccaf8e2a91f5f89589e91450358a: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/7cf4999898ed3a2881888e1ba1488166b77f1952ca2ed7ad516726455491dcd5: remove /nfs/for-machines/rw/docker/volumes/7cf4999898ed3a2881888e1ba1488166b77f1952ca2ed7ad516726455491dcd5: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/5ad0c7c2c1f9b857198ff569e7b19954e13478a9a070d4c7f63ed37a355563ab: remove /nfs/for-machines/rw/docker/volumes/5ad0c7c2c1f9b857198ff569e7b19954e13478a9a070d4c7f63ed37a355563ab: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/ffce49f56fa8d44942083a7dbe81b65c673e0bc28c5756fba73a8fa5767c22f4: remove /nfs/for-machines/rw/docker/volumes/ffce49f56fa8d44942083a7dbe81b65c673e0bc28c5756fba73a8fa5767c22f4: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/3e9fca966d7fa8cfba7abecc12df0884f135f1f489246976f19bd13d0a94baef: remove /nfs/for-machines/rw/docker/volumes/3e9fca966d7fa8cfba7abecc12df0884f135f1f489246976f19bd13d0a94baef: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/1fe904fee166f3c415754e462e5bc2e139fc6e485de086feb79abbee6bb9215d: remove /nfs/for-machines/rw/docker/volumes/1fe904fee166f3c415754e462e5bc2e139fc6e485de086feb79abbee6bb9215d: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/4faf14d4605c94a4a939c5b56aa121a05f5ab8715434401f660e7a10cf02d798: remove /nfs/for-machines/rw/docker/volumes/4faf14d4605c94a4a939c5b56aa121a05f5ab8715434401f660e7a10cf02d798: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/af4e49971367ccf21816700b67ceac8411d3a3791e4ea3a6707dda1ded666a6c: remove /nfs/for-machines/rw/docker/volumes/af4e49971367ccf21816700b67ceac8411d3a3791e4ea3a6707dda1ded666a6c: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/7c65bc014d43ed2022d85fbef7d7a31e1ed68039eb4256c1c660dca3b2cecad1: remove /nfs/for-machines/rw/docker/volumes/7c65bc014d43ed2022d85fbef7d7a31e1ed68039eb4256c1c660dca3b2cecad1: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/buildx_buildkit_builder0_state: remove /nfs/for-machines/rw/docker/volumes/buildx_buildkit_builder0_state: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/f01bc1d5ec901ff09ad9c5e0490354172effd1be8a888061778aef6a1a4d9884: remove /nfs/for-machines/rw/docker/volumes/f01bc1d5ec901ff09ad9c5e0490354172effd1be8a888061778aef6a1a4d9884: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/477cab9970ac75b95f87c804e35688956c749960b4d4892359a9dfb56bd907cc: remove /nfs/for-machines/rw/docker/volumes/477cab9970ac75b95f87c804e35688956c749960b4d4892359a9dfb56bd907cc: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/4943bde21f4a0f17f4577671ebc226d5e8e2b54cc99a604f8b7e0bae0a0620c6: remove /nfs/for-machines/rw/docker/volumes/4943bde21f4a0f17f4577671ebc226d5e8e2b54cc99a604f8b7e0bae0a0620c6: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/2c110bcd63f55ce951ad04da7ddd711c1a3963ea38a9403f88a20ee414def4ed: remove /nfs/for-machines/rw/docker/volumes/2c110bcd63f55ce951ad04da7ddd711c1a3963ea38a9403f88a20ee414def4ed: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/0ee6e494f10ebe3a785dc9895ff4b5f4d39599df6cdde444bcd7469953aba818: remove /nfs/for-machines/rw/docker/volumes/0ee6e494f10ebe3a785dc9895ff4b5f4d39599df6cdde444bcd7469953aba818: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/5d9f44099fb82a552ccdb10e48c8a83fef5ef7e0147fe463ef901b6eacfcf8a8: remove /nfs/for-machines/rw/docker/volumes/5d9f44099fb82a552ccdb10e48c8a83fef5ef7e0147fe463ef901b6eacfcf8a8: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/e1a9f9afdfe96914bd538691e53e6a3a18c3df7da16b67c5671ce8549e41e1b8: remove /nfs/for-machines/rw/docker/volumes/e1a9f9afdfe96914bd538691e53e6a3a18c3df7da16b67c5671ce8549e41e1b8: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/820c9d584210cb6f529d3b303cd44404c455a85e5f5e76ee6932f07a9bb32509: remove /nfs/for-machines/rw/docker/volumes/820c9d584210cb6f529d3b303cd44404c455a85e5f5e76ee6932f07a9bb32509: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/2eda6d34f5a52b3d2816dd02a260583526b84efbf44779f5ed25c2df61f97ee0: remove /nfs/for-machines/rw/docker/volumes/2eda6d34f5a52b3d2816dd02a260583526b84efbf44779f5ed25c2df61f97ee0: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/cd6f59832f8acd68df580cfcde387ad04fa7e210ee752596c546937e4d016bb6: remove /nfs/for-machines/rw/docker/volumes/cd6f59832f8acd68df580cfcde387ad04fa7e210ee752596c546937e4d016bb6: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/b7546c0315b16d46cf68952435ed704cc668c2efaec63f6aa71602ce5460480d: remove /nfs/for-machines/rw/docker/volumes/b7546c0315b16d46cf68952435ed704cc668c2efaec63f6aa71602ce5460480d: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/24e2dbb32c84db3beb7dda8ef399c80b9252febf90ab04e74f39ea6759024486: remove /nfs/for-machines/rw/docker/volumes/24e2dbb32c84db3beb7dda8ef399c80b9252febf90ab04e74f39ea6759024486: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/f98b63c766814fc21ce426e6deeba450f0096ea3b08c9b9024454ea389134f4c: remove /nfs/for-machines/rw/docker/volumes/f98b63c766814fc21ce426e6deeba450f0096ea3b08c9b9024454ea389134f4c: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/buildx_buildkit_container0_state: remove /nfs/for-machines/rw/docker/volumes/buildx_buildkit_container0_state: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/fe676a64c6a171eb7be36d007230885bc3d79078114d847da35c510c32565160: remove /nfs/for-machines/rw/docker/volumes/fe676a64c6a171eb7be36d007230885bc3d79078114d847da35c510c32565160: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/5a5f723c86669e7ad6f2b382b8523bdab1c4a67436b2ff6a512c70b86263bc37: remove /nfs/for-machines/rw/docker/volumes/5a5f723c86669e7ad6f2b382b8523bdab1c4a67436b2ff6a512c70b86263bc37: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/7538b3b4db3deefa5466e5d7418bf8832807c06cadbed362cbfa64e63e396aaa: remove /nfs/for-machines/rw/docker/volumes/7538b3b4db3deefa5466e5d7418bf8832807c06cadbed362cbfa64e63e396aaa: device or resource busy
unmount /nfs/for-machines/ro/docker/volumes/buildx_buildkit_multi-platform-builder0_state: remove /nfs/for-machines/rw/docker/volumes/buildx_buildkit_multi-platform-builder0_state: device or resource busy

To Reproduce

Start in-built Kubernetes cluster
Reset Kubernetes cluster via Settings... -> Kubernetes -> Reset Cluster

Expected behavior

Kubernetes cluster should reset

Diagnostic report (REQUIRED)

OrbStack info: Version: 1.8.0 Commit: 58b79a4a06c46666c70ca908a94b47fe70882fca (v1.8.0)

System info: macOS: 14.6.1 (23G93) CPU: arm64, 10 cores CPU model: Apple M1 Pro Model: MacBookPro18,1 Memory: 32 GiB

Diagnostic report failed: failed to upload: 500 Internal Server Error

Screenshots and additional context (optional)

No response

roderik commented 2 weeks ago

Resetting the full OrbStack works though. This has been an issue before 1.8, I think it is macOS 15 related

FabianKramm commented 2 weeks ago

@roderik thanks, yes resetting via Storage > Reset All Data worked for me

deshack commented 1 week ago

Resetting the full OrbStack works though. This has been an issue before 1.8, I think it is macOS 15 related

But the diagnostic report shows @FabianKramm is/was on MacOS 14.6.1

kdrag0n commented 1 week ago

This isn't related to OrbStack 1.8 or macOS 15.

orbstack / orbstack