-
Notifications
You must be signed in to change notification settings - Fork 8
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
traceroute command in the build/run image #139
Comments
can somebody help on this ? |
@doddisam hey there Sameer, can you discuss a bit more about your use case for needing this at run-time? Would it be helpful for all types of apps, or specific ones? We usually take a conservative approach to adding new packages to the stack images in order to limit vulnerability surface area, so I'd really like to understand fully what the benefit will be here. I see some associated CVEs with this package, like https://ubuntu.com/security/CVE-2023-46316, in which a fix is only available in the ESM (expanded security maintenance) version of the package which we cannot ship in the project. |
@sophiewigmore Thanks for the reply. I will be helpful if we have in all types of apps which uses this stack. In our environment many DEV teams deploy apps and they connect to external database, messaging and redis etc. Quite often there will be some network related issue or FW issue and it will be helpful to have traceroute for troubleshooting. App teams can work with network or FW team directly and provide traceroute outputs to destination server. |
@doddisam I'm not sure about this. I can see why including |
Hello Team,
Can we please include the traceroute command in the run image ?
It will be easy to troubleshoot the network and FW related issue.
-Sameer
The text was updated successfully, but these errors were encountered: