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 run in a Kubernetes cluster, does the LinuxGSM container remain running after failing to connect to the internet in entrypoint-user.sh? If not, I would have expected the cluster controller to restart the container, but retain the same pod, at which point networking should be present and the connections should succeed on the 2nd try.
It does seem problematic for the Kubernetes cluster if it is starting containers before networking is available.
Have an issue with linuxgsm failing because the entrypoint.sh tries to download and install before the network is initialized.
can a delay be added to wait for a full response from the internet before it begins the processes in entrypoint-user.sh?
a simple while loop works but obviously not if I have to reload the docker image
The text was updated successfully, but these errors were encountered: