[PR #647] [MERGED] Added DockProc to the list #1927

New Issue

GiteaMirror · 2026-04-15T05:51:50-05:00

GiteaMirror commented

2026-04-15 05:51:50 -05:00

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/647
Author: @cooperspencer
Created: 12/19/2018
Status: ✅ Merged
Merged: 12/19/2018
Merged by: @veggiemonk

Base: master ← Head: master

📝 Commits (1)

c1d5ba4 Added DockProc to the list

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

[Insert the URL to be listed]
https://gitlab.com/n0r1sk/dockproc

[Explain what the project is about and why it should be listed]
DockProc checks the I/O of containersr on processlevel. docker stats has the issue that it doesn't work with NFS-shares, so if you mounted an nfs share to your container, it doesn't see the read and written data. DockProc does this. And it is easy to connect the container processes to the pids on the host system.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines
The project submitted conforms to the quality standards outlined in the contribution guidelines
Go to the contribution guidelines and read it again.

RULES (because you probably didn't read the guidelines):

Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of README.md file.

FORMAT
- Use the following format: [Name](Link) - Description.
- [Name] should be the title of the project
- (Link) should be pointing to a GitHub repository, not to a website
- Description. should end with a full stop/period
- For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like By [@author](GitHub account)
ORDER: The entries are in lexical order (English letter order)
LABEL (Optional): Add one of the following icons next to the project name like [Name](Link) :icon: - Description.
- 💲 indicates if one needs a paying subscription to use the project.
- 🚧 indicates that the project is a work in progress/beta release.
- 💀 indicates that the project is obsolete, but still worth mentioning it.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/veggiemonk/awesome-docker/pull/647 **Author:** [@cooperspencer](https://github.com/cooperspencer) **Created:** 12/19/2018 **Status:** ✅ Merged **Merged:** 12/19/2018 **Merged by:** [@veggiemonk](https://github.com/veggiemonk) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`c1d5ba4`](https://github.com/veggiemonk/awesome-docker/commit/c1d5ba447622b2aab11ef8089676dd518d0ffccd) Added DockProc to the list ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description   **[Insert the URL to be listed]** https://gitlab.com/n0r1sk/dockproc **[Explain what the project is about and why it should be listed]** DockProc checks the I/O of containersr on processlevel. docker stats has the issue that it doesn't work with NFS-shares, so if you mounted an nfs share to your container, it doesn't see the read and written data. DockProc does this. And it is easy to connect the container processes to the pids on the host system. # By submitting this pull request I confirm I've read and complied with the below requirements. **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** - I have read and understood the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) - The project submitted conforms to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) - Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) and read it again. **RULES (because you probably didn't read the guidelines):** Links will be tested with [awesome_bot](https://github.com/dkhamsing/awesome_bot). Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of `README.md` file. - FORMAT - Use the following format: `[Name](Link) - Description.` - `[Name]` should be the title of the project - `(Link)` should be pointing to a GitHub repository, not to a website - `Description.` should end with a full stop/period - For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like `By [@author](GitHub account)` - ORDER: The entries are in lexical order (English letter order) - LABEL (Optional): Add one of the following icons next to the project name like ```[Name](Link) :icon: - Description.``` - :heavy_dollar_sign: indicates if one needs a paying subscription to use the project. - :construction: indicates that the project is a work in progress/beta release. - :skull: indicates that the project is obsolete, but still worth mentioning it. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-15 05:51:50 -05:00

GiteaMirror closed this issue

2026-04-15 05:51:50 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#1927