-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMI stopping docker containers before restart #175
Comments
"Restart" meaning restarting the instance? Docker daemon? |
It means stopping/starting the machine on the Amazon EC2 page, which is
a system restart.
…On 3 Apr 2017, at 10:44, dconathan wrote:
"Restart" meaning restarting the instance? Docker daemon?
--
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub:
#175 (comment)
|
We should probably pull NEXT and template
in |
Did you create a new AMI for this? I'm seeing an AMI with the name next_master_ami and ID |
No, I haven't?
Liam
…On Thu, Jun 29, 2017 at 5:36 PM, Scott Sievert ***@***.***> wrote:
Did you create a new AMI for this? I'm seeing an AMI with the name
next_master_ami and ID ami-2cd7341f.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#175 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEa8SeWuZ8WwvwI9KoaDDkZHqv55Fgjpks5sJCbrgaJpZM4MxtK7>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've seen an issue by Ian where he restarted many times and the docker containers got corrupted. Stopping before restart should help with this.
The text was updated successfully, but these errors were encountered: