25
,latest
ABRT is a set of tools to help users detect and report problems that occurred within their systems. In the contrary to other problem (crash) reporting tools, ABRT operates on operating system level and thus does not need to be integrated into monitored applications. Once you deploy ABRT, every applications running on your system is being monitored for crashes. There are certain limitations like applications intercepting their own crashes.
Automatic Bug Reporting Tool documentation
The images are build from official Fedora packages and ABRT development packages.
- core dump files (C/C++, Go)
- kernel oopses in journalctl
- kernel vmcores on host's file system
- regular file
- remote hosts
- Red Hat Bugzilla
- CentOS Bug Tracker
- Fedora Analysis Framework - FAF
To run start ABRT watching your system for problems run:
docker run -d --privileged -v /dev/log:/dev/log -v /var/run/systemd/journal/socket:/var/run/systemd/journal/socket -v /:/host -v /var/run/abrt:/var/run/abrt --pid=host --net=host --name NAME IMAGE
To list detected problems, analyze the problems and report the problems run:
docker exec -it NAME abrt
docker exec -it NAME abrt gdb
docker exec -it NAME abrt report
Pass -e ABRT_VERBOSE=NUM
on the run command line to make abrt producing more logs.
This image is officially supported on Docker version 1.12.3.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
Documentation for this image is available in the README.md
file in the
abrt/abrt-docker
GitHub repo.