Comments (1)
I also faced same issue, and luckily found reasons and workaround (using 2.8.1 version).
I've found out that this is a weaveworks/weave-kube:latest
image issue, specifically on the image shown as arm64
architecture in docker hub. Image uploaded to docker hub indicates that the image is arm64
architecture. But, actually binary inside that image is amd64
.
Workaround
As a simple fix, changing image tag inside weave-daemonset-k8s.yaml from latest
to 2.8.1
works.
You can download changed YAML file here: https://gist.github.com/jungin500/6ca26cc6f8e9b4c16988b50fe43a67f4
Causes
Both images (weaveworks/weave-kube:latest
, weaveworks/weave-npc:latest
) with architecture arm64
are uploaded on docker hub:
It is likely indicating the arm64
architecture, but actually is not:
$ docker inspect weaveworks/weave-npc@sha256:8cbee41d20340db9d861d94fd1396aca5b0bef569d89360862189414672d013b -f '{{ .Architecture }}'
amd64
$ docker inspect weaveworks/weave-kube@sha256:6b7b1c5bbb0589e6b294324aa3d7ee9316d49203c7c418bf087cbd7982ad62fa -f '{{ .Architecture }}'
amd64
I assume that root cause is misconfigured CI pipeline?
from weave.
Related Issues (20)
- connection between nodes is broken with weave net as CNI in on-premise kubernetes HOT 1
- After installing in k8s the pod cluster did not start
- weaveutil: line 23: syntax error: unexpected word (expecting ")") HOT 4
- clock: protect field access with lock to avoid possible data race HOT 1
- transport: protect field access with transport to avoid possible data race
- proto: protect field access with proto to avoid possible data race
- Network 10.42.0.0/16 overlaps with existing route 10.42.139.128/26 on host HOT 1
- Community Development of Weave Net
- Unable to fetch ConfigMap kube-system/weave-net to infer unique cluster ID
- Potential deadlock in vendor file
- Weave network unreachable upon restarting a VM HOT 1
- K8s kube-proxy and weave-net pods keep experiencing CrashLoopBackOff from time to time. HOT 1
- Vulnerability of dependency "golang.org/x/net" HOT 2
- Problem in starting weave-net pods on worker nodes
- Not able to watch applications/sources without secrets resources
- weave-net 0/2 Init:ImagePullBackOff, Kubernetes 1.23.7 on CloudStack 4.18.1
- how to download weavework docker plugin for non-internet installation HOT 1
- Docker 25+ error 'API error (400): client version 1.18 is too old.' HOT 7
- Documentation access HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from weave.