[caasp-beta] Antw: Re: Antw: Re: tcpdump
Martin.Weiss at suse.com
Wed Dec 6 02:37:12 MST 2017
> On Wed, Dec 06, Martin Weiss wrote:
>> An other approach for all that debugging purposes could be to use a special
>> docker image / docker container that delivers all the trouble shooting tools
>> required and run that with proper elevated rights..
>> Maybe we can deliver such an image for troubleshooting in general in the
> A special container was planned, don't know what happend with that.
> There is an open request from me to deliver a "Tool‑Module" like we
> have for SLE12, which could contain all this additional tools
> for trouble shooting.
Yes - but installing them and then updating and patching them will again increase the size and time required for patching / updating etc.
I sill would vote for a way to "temporarily" and "on demand" add the debugging tools required and remove them quickly after we do not need them anymore automatically..
(there are so many debugging tools that might be required in different situations that might use more disk space than the basic OS ;-))
>> On Tue, Dec 05, Jerry Hwang wrote:
>> > I see no tcpdump available in micro‑os v2.
>> > tried to install manually however it failed for read‑only file system (no
>> > surprise).
>> > any suggestion to have tcpdump?
>> The transactional‑update help says:
>> transactional‑update pkg install <your RPM>
>> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
>> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG
>> caasp‑beta mailing list
>> caasp‑beta at lists.suse.com
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG
> caasp‑beta mailing list
> caasp‑beta at lists.suse.com
More information about the caasp-beta