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

Create a local cluster fails if registry container is stopped #360

Open
jorgemoralespou opened this issue May 7, 2024 · 0 comments
Open
Labels
area/cli Issues that have any relation with the CLI bug Something isn't working

Comments

@jorgemoralespou
Copy link
Contributor

Describe the bug

When you create a local educates cluster if the registry already existed but is not running (with an ip/port binding) then cluster creation process fails at Linking local registry to cluster with:

Error: failed to create service for registry: unable to create registry headless service endpoint: EndpointSlice.discovery.k8s.io "registry-1" is invalid: [endpoints[0].addresses[0]: Invalid value: "": must be a valid IPv4 address, endpoints[0].addresses[0]: Invalid value: "": must be a valid IP address]

This is because the containerInspect of educates-registry here does not check for the container to be running and later the network.IPAddress of that container is empty (as it's stopped) and fails

Additional information

No response

@jorgemoralespou jorgemoralespou added bug Something isn't working area/cli Issues that have any relation with the CLI labels May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli Issues that have any relation with the CLI bug Something isn't working
Projects
Development

No branches or pull requests

1 participant