Bug 1877309
Summary: | toolbox deleted files from keybase kbfs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Aron Griffis <aron> |
Component: | podman | Assignee: | Qi Wang <qiwan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | bbaude, debarshir, dwalsh, harrymichal, jnovy, lsm5, mheon, rh.container.bot, santiago |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-01-28 12:16:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Aron Griffis
2020-09-09 11:26:25 UTC
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. |