Giter Club home page Giter Club logo

Comments (9)

dhess avatar dhess commented on May 15, 2024

FYI, with 519a372 and everything else the same as above:

 colima start --arch x86_64 --cpu 2 --memory 8                                                                                                                  ~
INFO[0000] starting colima                              
INFO[0000] creating and starting ...                     context=vm
INFO[0312] provisioning ...                              context=docker
INFO[0312] provisioning in VM ...                        context=docker
INFO[0540] restarting VM to complete setup ...           context=docker
INFO[0541] stopping ...                                  context=vm
INFO[0563] starting ...                                  context=vm
INFO[0799] starting ...                                  context=docker
INFO[0847] done

from colima.

abiosoft avatar abiosoft commented on May 15, 2024

@dhess there are major changes in the underlying linux distro. You would need to delete your existing instance and start afresh. i.e. colima delete

This would be part of the release notes for the next version.

Thanks.

from colima.

dhess avatar dhess commented on May 15, 2024

FYI, all of those colima start commands were run with no existing instance running (i.e., they had been preceded by colima delete).

from colima.

abiosoft avatar abiosoft commented on May 15, 2024

@dhess running cross-architecture with --with-kubernetes flag is most likely not going to work as cross-architecture is much slower.

Do you experience same behaviour with Docker and Containerd runtime (without kubernetes)?

from colima.

dhess avatar dhess commented on May 15, 2024

Do you experience same behaviour with Docker and Containerd runtime (without kubernetes)?

519a372 works fine with plain Docker and x86_64. I can create a cluster using Kind without any problem. (It's a bit slow, but useable.)

57469b9 doesn't work at all with plain Docker and x86_64.

I haven't tested containerd.

from colima.

abiosoft avatar abiosoft commented on May 15, 2024

@dhess a fix has been pushed to main branch. Can you kindly give it another try?

Thanks.

from colima.

dhess avatar dhess commented on May 15, 2024

Thanks! I'll try this out in the next day or two.

from colima.

dhess avatar dhess commented on May 15, 2024

On main, same problem with --with-kubernetes:

 colima start --with-kubernetes --arch x86_64 --cpu 2 --memory 8                                                  ~/git/hackworth-k8s-test
INFO[0000] starting colima                              
INFO[0000] creating and starting ...                     context=vm
INFO[0090] provisioning ...                              context=docker
INFO[0090] restarting VM to complete setup ...           context=docker
INFO[0090] stopping ...                                  context=vm
INFO[0101] starting ...                                  context=vm
INFO[0180] starting ...                                  context=docker
> command-line line 0: Unsupported option "gssapiauthentication"
> Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
WARN[0187] could not enable multi-arch images: exit status 1  context=docker
> command-line line 0: Unsupported option "gssapiauthentication"
> docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
> See 'docker run --help'.
WARN[0189] could not enable multi-arch images: exit status 125  context=docker
> command-line line 0: Unsupported option "gssapiauthentication"
> Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
WARN[0192] could not clear image cache for multi-arch images: exit status 1  context=docker
INFO[0193] downloading and installing ...                context=kubernetes
INFO[0249] loading oci images ...                        context=kubernetes
INFO[0327] starting ...                                  context=kubernetes
INFO[0334] updating config ...                           context=kubernetes
FATA[0334] error starting kubernetes: error at 'updating config': error fetching kubeconfig on guest: exit status 1

However, the non-Kubernetes x86_64 case now works well.

from colima.

abiosoft avatar abiosoft commented on May 15, 2024

Thanks, that suffices. cross-architecture is not expected to work with --with-kubernetes.

from colima.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.