-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
docker: prefer CMD to ENTRYPOINT for flexibility #8482
docker: prefer CMD to ENTRYPOINT for flexibility #8482
Conversation
b000da8
to
76df05d
Compare
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULContinuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-18405/ This is a comment from an automated CI system. |
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 arm8 part 1: Failed (click for details)Topotests Ubuntu 18.04 arm8 part 1: No useful log foundSuccessful on other platforms/tests
|
ci:rerun |
76df05d
to
42d723d
Compare
Missed |
Continuous Integration Result: SUCCESSFULContinuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-18418/ This is a comment from an automated CI system. |
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 amd64 part 7: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO7U18AMD64-18428/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 7:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-18428/artifact/TOPO7U18AMD64/ErrorLog/log_topotests.txt Successful on other platforms/tests
|
|
Specifying watchfrr as CMD instead of ENTRYPOINT allows one to easily override this command when starting a docker container. This allows simple, manual testing via (e.g.) bash. With ENTRYPOINT only the container will simply explode with an exit code if watchfrr exits. For instance one could start a shell session in this container via: ``` docker run --name test --rm -i -t <frr-container> bash ``` The default behavior (`docker run <frr-container>` with no command specified) is not changed. Signed-off-by: Wesley Coakley <wcoakley@nvidia.com>
42d723d
to
3a33be1
Compare
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-18442/ This is a comment from an automated CI system. |
Specifying watchfrr in Dockerfiles as CMD instead of ENTRYPOINT allows one to easily override the watchfrr command when starting a docker container. This allows simple, manual testing via (e.g.) bash. With ENTRYPOINT only the container will simply explode with an exit code if watchfrr exits.
If you tried to do this before you'd see this from
docker ps
:Which shows that /usr/lib/frr/docker-start (a wrapper around frrinit.sh) tried to start frrinit.sh with the
bash
parameter which clearly won't do anything. Now, one could start a shell session in this container via:The default behavior (
docker run <frr-container>
with no command specified) is not changed.