Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

machine rm: unable to clean up gvproxy: remove xxxx.pid: The process cannot access the file because it is being used by another process. #23472

Closed
edsantiago opened this issue Aug 1, 2024 · 3 comments
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine windows issue/bug on Windows

Comments

@edsantiago
Copy link
Member

In hyperv windows rootless:

podman machine init
  machine init rootless docker.sock check
...
  C> podman.exe machine rm --force 97cd37622ad8
  Error: unable to clean up gvproxy: remove C:\Users\ADMINI~1\AppData\Local\Temp\podman\gvproxy.pid: The process cannot access the file because it is being used by another process.

I don't know if this is the first instance. I rarely look at podman-machine flakes because there are more every day than any human can possibly handle. Every once in a while I peek at one or two, and if I see a new-to-me flake I'll file it.

@edsantiago edsantiago added flakes Flakes from Continuous Integration machine labels Aug 1, 2024
@edsantiago
Copy link
Member Author

Yeah, looks like a big one. This is just from yesterday, I don't have time to look at podman-machine flakes from the past week

  • windows : machine-hyperv podman windows rootless host sqlite
    • PR [CI:ALL] Bump to v5.2.0-rc3 #23462
      • 07-31 15:53 in podman machine init simple init with start
      • 07-31 15:53 in podman machine init machine init with cpus, disk size, memory, timezone
      • 07-31 15:53 in podman machine init machine init rootless docker.sock check
      • 07-31 15:53 in podman machine init machine init rootful with docker.sock check
      • 07-31 15:53 in podman machine start start simple machine
      • 07-31 15:53 in podman machine start start machine already started
      • 07-31 15:53 in podman machine start start machine with conflict on SSH port
      • 07-31 15:53 in podman machine start start only starts specified machine
      • 07-31 15:53 in podman machine start start two machines in parallel
      • 07-31 15:53 in podman machine ssh ssh to running machine and check os-type
      • 07-31 15:53 in run basic podman commands Basic ops
      • 07-31 15:53 in run basic podman commands Volume should be disabled by command line
      • 07-31 15:53 in run basic podman commands Podman ops with port forwarding and gvproxy
      • 07-31 15:53 in run basic podman commands podman volume on non-standard path
x x x x x x
machine-hyperv(14) podman(14) windows(14) rootless(14) host(14) sqlite(14)

@Luap99 Luap99 added the windows issue/bug on Windows label Aug 1, 2024
@edsantiago
Copy link
Member Author

A few more

x x x x x x
machine-hyperv(63) podman(63) windows(63) rootless(63) host(63) sqlite(63)

@baude
Copy link
Member

baude commented Aug 12, 2024

this error has been switched from a hard error to soft. we should no longer see it.

@baude baude closed this as completed Aug 12, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Nov 11, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Nov 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine windows issue/bug on Windows
Projects
None yet
Development

No branches or pull requests

3 participants