-
Notifications
You must be signed in to change notification settings - Fork 493
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
Host Container Unable to Create Container Task #3970
Comments
Hi @gitskamzn, Thanks for reaching out with this issue.
|
Hi @vigh-m - This is an ongoing issue that I see happening with instances using I can see the 10 seconds timeout here :
I see failed to delete container task. error: failed to delete task: context deadline exceeded:unknown error appear exactly 10 seconds after container task exited log message.
|
Just for scenarios like this one, is adding |
Hi,
|
Please see below:
Update Method being used: https://bottlerocket.dev/en/os/1.19.x/update/methods/in-place/ |
Do you loop after you are done with your Is this something you want to keep running every time? Why not setting all these configurations through user data, or even a bootstrap container with |
Image I'm using:
Bottlerocket K8s 1.29
VERSION_ID: 1.19.4
Build_ID=4f0a078e
What I expected to happen:
Expect container task to start every iteration.
What actually happened:
Container task fails to start after it encounters failure.
How to reproduce the problem:
I can see the container task start when a new node comes up. During its regular run, it fails to start again and complains the task already exists. This appears to happen when the previous deletion fails. I can see in logs the deletion of task fail with
context deadline exceeded
error.level=error msg=failed to delete container task" error="failed to delete task: context deadline exceeded: unknown"
level=error msg=failed to cleanup container" error="cannot delete running task taskname: failed precondition"
Subsequent runs are unable to get the task started as it seems to exist already.
The text was updated successfully, but these errors were encountered: