This repository has been archived by the owner on Dec 16, 2017. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
better detection of cloud-init finished during container creation
Merge of Mike McCracken's work from better_cloud_init_finished branch with minor updates to point to correct file location and not be fatal on init errors. Signed-off-by: Adam Stokes <adam.stokes@ubuntu.com>
- Loading branch information
Adam Stokes
committed
Nov 11, 2014
1 parent
e880b90
commit f20bb56
Showing
1 changed file
with
26 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f20bb56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you use the copy under rootfs instead of the one in /run in the container?
the cloud-init docs suggested that the /run symlink was better, to guarantee you aren't getting a stale copy from a previous run of the container
f20bb56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my tests that directory never contained the results.json file. Does it get removed automatically after cloud-init is finished?