302e3834a0
Once the job has failed and is respawned, the status becomes `docker respawn/post-start` after subsequent failures (as opposed to `docker stop/post-start`), so the post-start script needs to take this into account. I could not find specific documentation on the job transitioning to the `respawn/post-start` state, but this was observed on Ubuntu 14.04.2. Signed-off-by: Lewis Marshall <lewis@lmars.net> |
||
|---|---|---|
| .. | ||
| completion | ||
| desktop-integration | ||
| docker-device-tool | ||
| host-integration | ||
| httpserver | ||
| init | ||
| mkimage | ||
| syntax | ||
| udev | ||
| vagrant-docker | ||
| check-config.sh | ||
| download-frozen-image.sh | ||
| mkimage-alpine.sh | ||
| mkimage-arch-pacman.conf | ||
| mkimage-arch.sh | ||
| mkimage-busybox.sh | ||
| mkimage-crux.sh | ||
| mkimage-debootstrap.sh | ||
| mkimage-rinse.sh | ||
| mkimage-unittest.sh | ||
| mkimage-yum.sh | ||
| mkimage.sh | ||
| mkseccomp.pl | ||
| mkseccomp.sample | ||
| nuke-graph-directory.sh | ||
| project-stats.sh | ||
| README | ||
| report-issue.sh | ||
| REVIEWERS | ||
The `contrib` directory contains scripts, images, and other helpful things which are not part of the core docker distribution. Please note that they could be out of date, since they do not receive the same attention as the rest of the repository.