https://github.com/avitase/docker-valgrind
Docker container exposing a leading edge version of valgrind and decent cmake and g++ installations.
https://github.com/avitase/docker-valgrind
docker-image valgrind
Last synced: about 1 month ago
JSON representation
Docker container exposing a leading edge version of valgrind and decent cmake and g++ installations.
- Host: GitHub
- URL: https://github.com/avitase/docker-valgrind
- Owner: avitase
- Created: 2018-08-15T16:33:35.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2018-12-03T15:10:37.000Z (over 7 years ago)
- Last Synced: 2026-02-22T19:35:12.940Z (4 months ago)
- Topics: docker-image, valgrind
- Language: Shell
- Homepage:
- Size: 13.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Docker-Valgrind
The container exposes a leading edge version of `valgrind` and decent `cmake` and `g++` installations. The idea is to mount the root directory of your project to `/input` (read-only), compile it in the container to a temporary directory and show the logged output.
For example, consider the test project we provide in [test/](test/):
```
> tree test/
test/
├── CMakeLists.txt
└── test.cxx
```
The `WORKDIR` is set to `/home/valgrind/build`, such that one can safely compile this test project after mounting `-v "$SRC":/input:ro` , via `cmake /input/ && make`. Since `WORKDIR` is not part of a mounted volume, the result does not appear outside of the container. This workflow can conveniently be wrapped in a shell script, for instance as we did in [valgrind.sh](valgrind.sh).
## Docker Pull Command
The container is accessible via the [Docker Hub](https://hub.docker.com/r/avitase/docker-valgrind/): `docker pull avitase/docker-valgrind`.
You can create your own `Dockerfile` and install additional dependencies of your project via `apk`, for example:
```
FROM avitase/docker-valgrind:latest
USER root
apk add --update gtest
USER ${USERNAME}
```