Hide Forgot
Description of problem: I have a bunch of files in Keybase KBFS. This is a streaming FUSE filesystem that stores encrypted in the cloud. https://book.keybase.io/docs/files I used toolbox enter, then cleaned up with toolbox reset. The reset operation took a long time... turns out it was because it was "cleaning up" all my files in Keybase. Version-Release number of selected component (if applicable): 0.0.95 How reproducible: It happened yesterday, I'm not anxious to try again Steps to Reproduce: 1. Get set up with https://keybase.io/ 2. Store some files in /keybase/ which is a redirector to your personal kbfs mount ✸ ls -l /keybase/ private -> /run/user/10208/keybase/kbfs/private public -> /run/user/10208/keybase/kbfs/public team -> /run/user/10208/keybase/kbfs/team 3. Make a toolbox 4. toolbox reset Actual results: Cleaned out keybase Expected results: Cluttered keybase Additional info: You can recover keybase files, dir by dir, with commands such as keybase fs recover --reltime=1h /keybase/private/agriffis/\*
Are you saying that you lost the contents of /run/user/10208/keybase? 'toolbox reset' is nothing but a wrapper around 'podman system reset'. Unless you use Toolbox's --assumeyes or -y flag, it should prompt you before proceeding to deleting anything. Even if you choose to proceed, it's meant to only clean up Podman's state, not anything else. I just tried 'podman system reset' on my machine with Podman 2.0.5, and as far as I can make out, it didn't delete anything that it shouldn't have. So, if it touched /run/user/10208/keybase, then it would appear to be a Podman bug.
This does remind me of https://github.com/containers/podman/issues/4831 but I thought that it was fixed a while back. What's the output of 'rpm -q podman'? Anyway, reassigning, because this is just 'podman system reset'.
Yeah, it does look like that bug podman-2.0.6-1.fc32.x86_64
So you are saying that `podman system reset` is removing content from /run/user/10208/keybase?
Yes, that's what I'm saying. Though I haven't tried it again since the first time it cleaned out my keybase filesystem.
Qi could you verify this?
I failed to regenerate this issue. I was using Version:2.0.6.