- Install systemd-coredump in base o/s
- Remove existing simple coredump facility
- Enable persistent journald to store coredump history
- Minimal default coredump configuration
- Added a coredump-config service to generate coredump configuration

Core files generated by kernel are created by the host o/s and also stored
on host o/s. This applies for processes running inside container as well.
Containers do not have access to journal as well as core files. Containers
are supposed to have limited access to host o/s and core files and journal
may contain sensitive information.

Toimprove debugging of crashes inside a container following changes are made:

- when INSTALL_DEBUG_TOOLS=y is set in the build. systemd-coredump tool
is installed in all containers beside gdb

- When SONIC_DEBUGGING_ON=y is set in the build,
  /var/log/journal and /var/lib/systemd/coredump are mapped inside container

To inspect a core file, from a container shell, issue below commands

docker exec -ti <container-name> /bin/bash

…into a container