This repository was archived by the owner on Aug 28, 2019. It is now read-only.
Permalink
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 12 commits
- 739 files changed
- 1 contributor
Commits on Aug 2, 2019
-
Fix build and issues with latest docker
- Vendor all the dependencies - Use 'go mod' - Minor fixes - Cannot pass "username" to dockerun, must pass "uid" - Update container config location - Pass current env when nsentering (TODO: Probably should use nsenter?) - Don't panic when docker is not installed - Fix 'go vet' errors
Commits on Aug 8, 2019
-
- Use docker client API - vendor all dependencies - Remove unused files
Commits on Aug 21, 2019
Commits on Aug 28, 2019
Commits on Dec 2, 2019
-
Fix "docker exec" orphan process
When this "dockersh" process is signalled/killed (like when ssh disconnects due to network issue etc), due to a docker bug, processes that are running inside 'docker exec' are left as they are i.e., they will continue to run. This can add up quite a bit of processes over the time. See here for more information: moby/moby#9098 Until that is fixed, we will handle it here by: - Have the pid of exec'ed bash at /tmp/dockersh-exec-${this_process_pid} - Install a signal handler here that will send SIGHUP to the pid stored in /tmp/dockersh-exec-${this_process_pid}
-
-
Commits on Dec 3, 2019
-
It is possible that child process (i.e., "docker exec") can get SIGHUP and exit before dockersh process gets notified. So we will run docker exec cleanup in both cases.
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master