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
It took me 10+ hours to figure the right combination of steps to make containers start up. However, the container-cni library, while recognized by minikube, doesn't seem to actually configure the networking correctly in minikube because the pods are not able to talk to the outside internet (i.e. the containers still seem to be on host/null networks under docker0 instead of on the cni0 bridge created by containerd-cni).
Once we get this figured out, for long term I really think this makes sense to have these pieces be offered pre-installed by Travis similar to what it does for:
services:
- docker
The text was updated successfully, but these errors were encountered:
The created pods have external network connectivity (ping outside world fine), but I am hitting a MTU mismatch issue like gliderlabs/docker-alpine#307 . Once I get that figured out I can make a PR to replace the current .travis.yml here.
Using minikube versions 1.24 and later on Travis requires additional steps like:
It took me 10+ hours to figure the right combination of steps to make containers start up. However, the container-cni library, while recognized by minikube, doesn't seem to actually configure the networking correctly in minikube because the pods are not able to talk to the outside internet (i.e. the containers still seem to be on host/null networks under docker0 instead of on the cni0 bridge created by containerd-cni).
Once we get this figured out, for long term I really think this makes sense to have these pieces be offered pre-installed by Travis similar to what it does for:
The text was updated successfully, but these errors were encountered: