Skip to content

fix: empty container IP address while it's attached to another container#118

Open
0w0mewo wants to merge 2 commits intoaacebedo:masterfrom
0w0mewo:fix-container-ip
Open

fix: empty container IP address while it's attached to another container#118
0w0mewo wants to merge 2 commits intoaacebedo:masterfrom
0w0mewo:fix-container-ip

Conversation

@0w0mewo
Copy link
Copy Markdown

@0w0mewo 0w0mewo commented Jun 6, 2024

When a container is attached to another container's networking stack, the IP address of the container is empty and resulting DockerManager keep triggering retry and restart.
This PR fills the empty IP address with the attached container's IP address.

Note: The restart loop triggered even the com.dnsdock.ignore label has added because overrideFromLabels() and overrideFromEnv() will return nil and cause DockerManger.getService() returns a non-nil error when service == nil and trigger the restart loop. Therefore, I explicitly add a field in Service struct to mark the service as 'ignored' instead of returning nil,

0w0mewo added 2 commits June 6, 2024 18:34
When a container's networking stack is attached to another container, the
IP address of the container is empty and resulting DockerManager keep triggering retry and restart.
Note: The restart loop triggered even the `com.dnsdock.ignore` label has added.
@0w0mewo 0w0mewo changed the title fix: empty container ip while it's attach to another container fix: empty container IP address while it's attached to another container Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant