Skip to content

Conversation

taylorsilva
Copy link
Member

Changes proposed by this PR

We found that if a container wasn't correctly made, specifically if the /etc/hosts file of the container wasn't populated with the containers IP, container cleanup would fail with this error:

resume container traffic: error getting container IP: ip not found for container handle: 0ce036f8-aa2a-4bea-acbd-8ee48e5fa63b

We can ignore this error when deleting a container because it tells us there are no iptables rules to remove anyways. We can probably continue deleting the container and will delete it successfully.

Release Note

  • Make container deletion more robust by continuing to delete a container even if we get errors related to reading the containers /etc/host file

@taylorsilva taylorsilva requested a review from a team as a code owner February 28, 2025 18:02
We found that if a container wasn't correctly made, specifically if the
`/etc/hosts` file of the container wasn't populated with the containers
IP, container cleanup would fail with this error:

```
resume container traffic: error getting container IP: ip not found for container handle: 0ce036f8-aa2a-4bea-acbd-8ee48e5fa63b
```

We can ignore this error when deleting a container because it tells us
there are no iptables rules to remove anyways. We can probably continue
deleting the container and will delete it successfully.

Signed-off-by: Taylor Silva <dev@taydev.net>
@taylorsilva taylorsilva force-pushed the ignore-container-ip-lookup-errors branch from f5ec8a9 to d24a423 Compare February 28, 2025 18:11
@taylorsilva taylorsilva merged commit 59c5e67 into master Feb 28, 2025
11 checks passed
@taylorsilva taylorsilva deleted the ignore-container-ip-lookup-errors branch February 28, 2025 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant