You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the designated ingress port is already in use, the project fails to come up with an obscure stack trace (this appears to be the same error as in other cases when the k3d cluster fails to be created, e.g. with an incompatible k3d version).
# ...
\[ERROR] Somethingwentcompletelywrongwiththeclusterspinup (orwegotatimeout).
# ...File"/home/veit/.local/lib/python3.8/site-packages/src/cli/project.py", line261, inupTelepresence(cluster.storage.get()).start()
File"/home/veit/.local/lib/python3.8/site-packages/src/local/system.py", line76, in__init__raiseValueError("Project does not contain the kubeconfigPath parameter")
ValueError: ProjectdoesnotcontainthekubeconfigPathparameter
Some foreseeable errors could be checked against in advance (like if the ingress port is available on the host). Also, why not capture the error output of the k3d cluster create command, which in this case would be something like:
ERRO[0021] Failed Cluster Start: Failed to add one or more helper nodes: runtime failed to start node 'k3d-unikube-mumpiz-serverlb': docker failed to start container for node 'k3d-unikube-mumpiz-serverlb': Error response from daemon: driver failed programming external connectivity on endpoint k3d-unikube-mumpiz-serverlb (c58c63548f30caa8b752b2d763ff4990e465e55f6210abe7166e464fdf2004f9): Bind for 0.0.0.0:61348 failed: port is already allocated
ERRO[0021] Failed to create cluster >>> Rolling Back
When the designated ingress port is already in use, the project fails to come up with an obscure stack trace (this appears to be the same error as in other cases when the k3d cluster fails to be created, e.g. with an incompatible k3d version).
Some foreseeable errors could be checked against in advance (like if the ingress port is available on the host). Also, why not capture the error output of the
k3d cluster create
command, which in this case would be something like:That would immediately reveal the problem.
The text was updated successfully, but these errors were encountered: