|
Re: [cni] do_compile network issue behind proxy for Hardknott
:-D
Awesome, thanks! I will be more than happy to evaluate such changes here in my builds.
BR,
/Joakim
:-D
Awesome, thanks! I will be more than happy to evaluate such changes here in my builds.
BR,
/Joakim
|
By
Joakim Roubert
·
#6565
·
|
|
Re: [cni] do_compile network issue behind proxy for Hardknott
I have a note written on the paper in front of me "fix cni build for
no-network", and a half started fix. :D
So yes, cni is doing some fetches, due to missing go dependencies and
trying to do a
I have a note written on the paper in front of me "fix cni build for
no-network", and a half started fix. :D
So yes, cni is doing some fetches, due to missing go dependencies and
trying to do a
|
By
Bruce Ashfield
·
#6564
·
|
|
[cni] do_compile network issue behind proxy for Hardknott
Hi!
After upgrade to Hardknott from Gatesgarth, building cni on a machine behind a proxy gives me network errors:
run.do_compile.18062' failed with exit code 1: go:
Hi!
After upgrade to Hardknott from Gatesgarth, building cni on a machine behind a proxy gives me network errors:
run.do_compile.18062' failed with exit code 1: go:
|
By
Joakim Roubert
·
#6563
·
|
|
Re: [PATCH] runc-docker: adjust patch to fit latest version
It works.
Got it. Thanks a lot.
Regards,
Kai
--
Kai Kang
Wind River Linux
It works.
Got it. Thanks a lot.
Regards,
Kai
--
Kai Kang
Wind River Linux
|
By
kai
·
#6562
·
|
|
Re: Networking issue with l3s when using systemd
<richard.purdie@...> wrote:
I'm sure we'll hear if someone is expecting networkd to manage their
veth devices :D
Either way works for me, I just lean towards keeping core very
<richard.purdie@...> wrote:
I'm sure we'll hear if someone is expecting networkd to manage their
veth devices :D
Either way works for me, I just lean towards keeping core very
|
By
Bruce Ashfield
·
#6561
·
|
|
Re: [PATCH] runc-docker: adjust patch to fit latest version
I just pushed the fix.
By "second variant", I just mean the runc-docker.
At one point, it was significant, but it is basically identical to the
runc-opencontainers one at this point, with a couple
I just pushed the fix.
By "second variant", I just mean the runc-docker.
At one point, it was significant, but it is basically identical to the
runc-opencontainers one at this point, with a couple
|
By
Bruce Ashfield
·
#6560
·
|
|
Re: [PATCH] runc-docker: adjust patch to fit latest version
Hi Bruce,
It breaks do_patch again. And what is the "second variant" you've mentioned, please?
Regards,
Kai
-- Kai KangWind River Linux
Hi Bruce,
It breaks do_patch again. And what is the "second variant" you've mentioned, please?
Regards,
Kai
-- Kai KangWind River Linux
|
By
kai
·
#6559
·
|
|
Re: Networking issue with l3s when using systemd
FWIW I suspect the veth change should be ok for OE-Core if I understandÂ
things correctly.
Cheers,
Richard
FWIW I suspect the veth change should be ok for OE-Core if I understandÂ
things correctly.
Cheers,
Richard
|
By
Richard Purdie
·
#6558
·
|
|
Re: Networking issue with l3s when using systemd
Perhaps, but it is probably a good idea to have the default as broad
as possible. If someone comes up with an alternate requirement, you'd
end up having a harder time keeping them both working in
Perhaps, but it is probably a good idea to have the default as broad
as possible. If someone comes up with an alternate requirement, you'd
end up having a harder time keeping them both working in
|
By
Bruce Ashfield
·
#6557
·
|
|
Re: Networking issue with l3s when using systemd
Hey Bruce,
I understand that changing things can be difficult once launched.
But looking at the systemd documentation here https://wiki.archlinux.org/title/systemd-networkd and in the note that says
Hey Bruce,
I understand that changing things can be difficult once launched.
But looking at the systemd documentation here https://wiki.archlinux.org/title/systemd-networkd and in the note that says
|
By
Matt Spencer
·
#6556
·
|
|
Re: Networking issue with l3s when using systemd
This particular issue is known, in the sense that we have run into it before.
At a minimum, I need to warn about it in the k3s README files.
I created the cni bbclass to manage potentially
This particular issue is known, in the sense that we have run into it before.
At a minimum, I need to warn about it in the k3s README files.
I created the cni bbclass to manage potentially
|
By
Bruce Ashfield
·
#6555
·
|
|
Networking issue with l3s when using systemd
Hi all
There seems to be a networking problem with k3s when using systemd. The problem manifests in that none of the kube-system management containers are able to communicate with eachother.
The root
Hi all
There seems to be a networking problem with k3s when using systemd. The problem manifests in that none of the kube-system management containers are able to communicate with eachother.
The root
|
By
Matt Spencer
·
#6554
·
|
|
Re: [PATCH] novnc: Correct permission error
merged.
Bruce
In message: [meta-virtualization] [PATCH] novnc: Correct permission error
on 07/06/2021 zangrc wrote:
merged.
Bruce
In message: [meta-virtualization] [PATCH] novnc: Correct permission error
on 07/06/2021 zangrc wrote:
|
By
Bruce Ashfield
·
#6553
·
|
|
Re: [hardnott][PATCH] kubernetes: fix CVE-2021-20206
disregard this please!
By
sakib.sajal@...
·
#6552
·
|
|
[hardnott][PATCH 1/2] kubernetes: fix CVE-2021-25737
Updating EndpointSlice validation to match Endpoints validation
Signed-off-by: Sakib Sajal <sakib.sajal@...>
---
.../kubernetes/CVE-2021-25737.patch | 213 ++++++++++++++++++
Updating EndpointSlice validation to match Endpoints validation
Signed-off-by: Sakib Sajal <sakib.sajal@...>
---
.../kubernetes/CVE-2021-25737.patch | 213 ++++++++++++++++++
|
By
sakib.sajal@...
·
#6551
·
|
|
[hardnott][PATCH 2/2] kubernetes: fix CVE-2021-20206
Bump containernetworking/cni to v0.8.1
Signed-off-by: Sakib Sajal <sakib.sajal@...>
---
.../kubernetes/CVE-2021-20206.patch | 97 +++++++++++++++++++
Bump containernetworking/cni to v0.8.1
Signed-off-by: Sakib Sajal <sakib.sajal@...>
---
.../kubernetes/CVE-2021-20206.patch | 97 +++++++++++++++++++
|
By
sakib.sajal@...
·
#6550
·
|
|
[hardnott][PATCH] kubernetes: fix CVE-2021-20206
Bump containernetworking/cni to v0.8.1
Signed-off-by: Sakib Sajal <sakib.sajal@...>
---
.../kubernetes/CVE-2021-20206.patch | 97 +++++++++++++++++++
Bump containernetworking/cni to v0.8.1
Signed-off-by: Sakib Sajal <sakib.sajal@...>
---
.../kubernetes/CVE-2021-20206.patch | 97 +++++++++++++++++++
|
By
sakib.sajal@...
·
#6549
·
|
|
[PATCH] novnc: Correct permission error
The permission of novnc-server was set incorrectly when copying.
Signed-off-by: Zang Ruochen <zangrc.fnst@...>
---
meta-openstack/recipes-extended/novnc/novnc_git.bb | 4 ++--
1 file
The permission of novnc-server was set incorrectly when copying.
Signed-off-by: Zang Ruochen <zangrc.fnst@...>
---
meta-openstack/recipes-extended/novnc/novnc_git.bb | 4 ++--
1 file
|
By
zangrc
·
#6548
·
|
|
[PATCH] ceph: Fix compile error with snappy
snappy changed a data type in the last update, this is a known
issue in ceph.
Signed-off-by: Saul Wold <saul.wold@...>
---
...mpressor.h-fix-snappy-compiler-error.patch | 30
snappy changed a data type in the last update, this is a known
issue in ceph.
Signed-off-by: Saul Wold <saul.wold@...>
---
...mpressor.h-fix-snappy-compiler-error.patch | 30
|
By
Saul Wold
·
#6547
·
|
|
Re: [PATCH] nativesdk-sloci-image: add recipe
Thanks for the follow up!
Bruce
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
Thanks for the follow up!
Bruce
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
|
By
Bruce Ashfield
·
#6546
·
|