Skip to content
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

Dirty rebooting after update on Amazon ECS Instances #2597

Open
ethicalmohit opened this issue Jun 25, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@ethicalmohit
Copy link

commented Jun 25, 2019

Issue Report

Container Linux is rebooting after updates is killing docker container running on the host to exit without clean draining. I am using reboot immediately after update strategy.

Bug

Container Linux Version

cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=2079.6.0
VERSION_ID=2079.6.0
BUILD_ID=2019-06-11-0821
PRETTY_NAME="Container Linux by CoreOS 2079.6.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

...
BUG_REPORT_URL="https://issues.coreos.com"

Environment

What hardware/cloud provider/hypervisor is being used to run Container Linux?

m5.large, m5.xlarge

Expected Behavior

The tasks should cleanly exit.

Actual Behavior

The tasks don't know about the host is getting rebooted and it exited.

Reproduction Steps

  1. Spin up AWS ECS Cluster
  2. Run some tasks.
  3. Update and let coreos reboot.
@ajeddeloh

This comment has been minimized.

Copy link

commented Jun 25, 2019

systemd tries to cleanly shut down services when rebooting. This means it should exec the ExecStop= entries in units. See https://coreos.com/os/docs/latest/getting-started-with-systemd.html for an example. Would that help in your case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.