This repository has been archived by the owner on Feb 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 445
pidof: unrecognized option: x #50
Comments
we encounter the same problem when using the lastest image (2 days old) since there are no other image tags than |
@svenmueller We currently forked: https://github.com/Financial-Times/docker-gc and built: |
@Zapadlo Your container has the same issue: [ ~ ] docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v /etc:/etc coco/docker-gc
pidof: unrecognized option: x
BusyBox v1.23.2 (2015-04-24 15:46:01 GMT) multi-call binary.
Usage: pidof [OPTIONS] [NAME]...
List PIDs of all processes with names that match NAMEs
-s Show only one PID
-o PID Omit given pid
Use %PPID to omit pid of pidof's parent |
@onibox Thank you, pushed and tagged latest. Should be fine now. |
@Zapadlo If you want to open a PR, I'd be happy to merge it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, we are using the docker-gc as a docker image running on our cluster. It is run as a systemd service with following
ExecStart
:docker run --name %p --rm -v /var/run/docker.sock:/var/run/docker.sock spotify/docker-gc || docker rmi spotify/docker-gc
.Issue we are seeing is:
And it seems like the process doesn't get run.
Thanks
[Edit] I suspect this is to do with difference of running natively vs running in a container that is using alpine:
[Edit#2] Can theonlydoo@7fc4110 use
-s
instead of-x
as that option is available in BusyBox v1.23.2 (2015-04-24 15:46:01 GMT) multi-call binary. used by Alpine?The text was updated successfully, but these errors were encountered: