docker:networking:ping_command_not_found
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| docker:networking:ping_command_not_found [2020/07/15 09:30] – external edit 127.0.0.1 | docker:networking:ping_command_not_found [2025/07/25 14:43] (current) – peter | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Docker - Networking - Ping command not found ====== | ====== Docker - Networking - Ping command not found ====== | ||
| - | Docker container | + | ===== Check if ping works ===== |
| + | |||
| + | Run a Docker container | ||
| <code bash> | <code bash> | ||
| Line 7: | Line 9: | ||
| </ | </ | ||
| - | Then trying | + | Then try a ping: |
| <code bash> | <code bash> | ||
| Line 16: | Line 18: | ||
| ---- | ---- | ||
| + | ===== Install ping ===== | ||
| - | Docker images are pretty minimal, | + | Docker images are pretty minimal, |
| <code bash> | <code bash> | ||
| Line 24: | Line 27: | ||
| </ | </ | ||
| - | Chances are you don't need ping your image, and just want to use it for testing purposes. Above example will help you out. | + | |
| But if you need ping to exist on your image, you can create a Dockerfile or commit the container you ran the above commands in to a new image. | But if you need ping to exist on your image, you can create a Dockerfile or commit the container you ran the above commands in to a new image. | ||
| Line 60: | Line 63: | ||
| docker run -it ubuntu_with_ping | docker run -it ubuntu_with_ping | ||
| </ | </ | ||
| + | |||
| + | ---- | ||
| + | |||
docker/networking/ping_command_not_found.1594805433.txt.gz · Last modified: 2020/07/15 09:30 by 127.0.0.1