-
Notifications
You must be signed in to change notification settings - Fork 146
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
curl - check script #29
Comments
I noticed that the docker image on docker-hub does not match the Dockerfile. |
@ReSearchITEng it's the same file use on github and for the docker image docker-keepalived/image/Dockerfile Line 36 in ed415f6
|
yes, it's there in the Dockerfile, but not in the images... docker run -d --name test osixia/keepalived:latest
docker exec test curl
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"curl\": executable file not found in $PATH"
docker exec test /bin/curl
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"/bin/curl\": stat /bin/curl: no such file or directory"
[docker@docker01:0 ~]$ docker exec -ti test bash
bash-4.3# curl
bash: curl: command not found
bash-4.3# which bash
/bin/bash
bash-4.3# which curl
bash-4.3# which curl | wc -l
0 |
in the same run statement curl is installed to download keepalived sources and then removed, so yes it's not available in the docker image install : docker-keepalived/image/Dockerfile Line 11 in ed415f6
removed docker-keepalived/image/Dockerfile Line 36 in ed415f6
|
Oh, sorry, I see the remove. Should you agree with it, here is the PR: #30 |
Thanks for the PR will try no make a release later today :) |
Thanks for accepting the change. |
@BertrandGouny ticket can be closed, curl exists inside the container. |
Provided that keepalived is mainly used for web purposes, and provided that keepalived usually needs a check script, I think the image needs curl package.
(see also #27).
The text was updated successfully, but these errors were encountered: