New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cilium fails to launch on ARM64: Binary cilium-envoy cannot be executed #17467
Comments
@joestringer Is this something that Cilium is adjusting for? Just tried 1.10.5 on an arm64 host and got the same error. |
@jovalle I'm not aware of any Cilium settings for this, but I was not deeply involved in the ARM64 efforts.My interpretation of the answer provided by the user in Slack (copied above) was that they had to recompile their kernel to support these images. You might be able to find out more info by joining the Cilium slack and asking around, perhaps in the #arm64 channel. |
If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. cilium#17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com>
If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. #17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com>
If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. #17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com>
[ upstream commit a46e572 ] If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. cilium#17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com> Signed-off-by: Louis DeLosSantos <louis.delos@isovalent.com>
[ upstream commit a46e572 ] If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. #17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com> Signed-off-by: Louis DeLosSantos <louis.delos@isovalent.com>
[ upstream commit a46e572 ] If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. cilium#17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com> Signed-off-by: Louis DeLosSantos <louis.delos@isovalent.com> Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
[ upstream commit a46e572 ] If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. cilium#17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com> Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. cilium#17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com>
[ upstream commit a46e572 ] If '--enable-l7-proxy' is set to 'false', there is no point in performing the Envoy version check, and so it should be automatically disabled. One of the motivations for this change is that in some scenarios it's necessary to disable the L7 proxy to allow Cilium to start (eg. #17467), but specifying '--enable-l7-proxy=false' is not enough due to the version check still being performed in this situation. This commit attempts to improve the UX by disabling the version check if Envoy itself is disabled. Signed-off-by: Bruno M. Custódio <brunomcustodio@gmail.com> Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
… we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
…re eBPF/net stuff - enable more eBPF/net stuff for Cilium - switch to 48-bit virtual addresses, so we're tcmalloc compatible - see cilium/cilium#17467 - see envoyproxy/envoy#15235 (comment)
A user on Slack reports:
Upon further investigation by attempting to run the binary directly, they saw:
Upstream tcmalloc has a related issue, google/tcmalloc#33 .
The user reports that adjusting tcmalloc configuration, the problem goes away:
The text was updated successfully, but these errors were encountered: