Skip to content
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.

Incorrect process detection ("Process is already running") #111

Closed
drewmnoel opened this issue Jun 27, 2016 · 1 comment · Fixed by #112
Closed

Incorrect process detection ("Process is already running") #111

drewmnoel opened this issue Jun 27, 2016 · 1 comment · Fixed by #112

Comments

@drewmnoel
Copy link

Description

The new process detection (in 420558e) seems to be problematic when run with sudo. This is probably because sudo creates another copy of the process entry with root permissions, and then runs that. So there will be two copies in the process list.

If I switch to root, the command works just fine.

How to reproduce

  1. Run sudo docker-gc

What do you expect

Command completes successfully

What happened instead

docker-gc detects the original sudo request as a separate process, and refuses to run

Software:

  • bash version: GNU bash, version 4.3.42(1)-release
  • fgrep version: grep (GNU grep) 2.25
  • sudo version: Sudo version 1.8.16

Full backtrace

$ sudo docker-gc
[Mon Jun 27 11:47:26 EDT 2016] : docker-gc : Process is already running with PID 6817
@mattnworb
Copy link
Member

hey @drewmnoel thanks for the heads up. I've reverted that previous change at #112

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants