NEXT
NEXT copied to clipboard
nextml
AMI stopping docker containers before restart
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.
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: https://github.com/nextml/NEXT/issues/175#issuecomment-291183554
We should probably pull NEXT and template docker-compose.yml in an ExecStartPre, and then do
ExecStart=docker-compose -f $COMPOSE_FILE up
ExecStop=docker-compose -f $COMPOSE_FILE down
in next.service.
Did you create a new AMI for this? I'm seeing an AMI with the name next_master_ami and ID ami-2cd7341f.
No, I haven't?
Liam
On Thu, Jun 29, 2017 at 5:36 PM, Scott Sievert [email protected] 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 https://github.com/nextml/NEXT/issues/175#issuecomment-312127179, or mute the thread https://github.com/notifications/unsubscribe-auth/AEa8SeWuZ8WwvwI9KoaDDkZHqv55Fgjpks5sJCbrgaJpZM4MxtK7 .