-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
etcd cannot run on arm64 #10677
Comments
Are you referring to the warning message? It is a warning message for not officially supported platform. Please see [1]. |
Thanks. I've set the environment variable
I think it's not a warning, an error occurred while starting the etcd.service
I'm verifying kubernetes on a new operating system and need the etcd server, I wonder is there any way to prove that the operating system is not compatible with it. |
Could you share the etcd log? |
sorry, because we are an Intranet, so the full log cannot be copied out.
Is it possible that there is something wrong with my system setup? |
These are not etcd logs. Can you check |
I restarted the etcd service.
And then
There is no warning message about "unsupported platform... arm64..." in the logs, now I think there is something wrong with the etcd.service file, but I used the same etcd.servcie file on another amd64 platform, and it worked. |
@Zhang-zhixiong
I have tested it with kubernetes, and the result is OK.
|
I run the following command:
and the result is OK, the log is same to you
the following is my etcd systemd service files:
but it still couldn't start the etcd.service |
@lubinsz a related checklist here - https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/supported-platform.md#supporting-a-new-system-platform Also a related issue tracking checklist #10318 |
Hello! Just now,I face with the same problem when I try to install etcd on arm64. |
In my case I changed /etc/default/etcd and added ETCD_UNSUPPORTED_ARCH=arm to the end of the file. I also had to grant etcd account permissions to folder |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
I was able to repro this on arm64.
Confirm that the env exists:
|
FYI: Bolt data format does not handle endianess properly, i.e. data written on little-endian architecture will not be accessible on big-endian architectures. Make sure you don't transfer data between architectures or use your ARM in little-endian mode. |
This may be an extreme edge case, but it tripped me up so sharing if useful to even one other person. I have many pi systems of different vintages, using different images. I picked three to build out an etcd cluster but neglected to do a All the way from the Go install you have to follow slightly different paths for aarch64/arm64 and arm7/32-bit, which of course sounds obvious in retrospect. The slight trap is that it actually almost/sorta/kinda works when you do it wrong. aarch64/arm64Before you even download Go, update .bashrc with
Source that, then, use a script like below to install Go
Then do your basic etcd source clone and build $ git clone -b v3.4.16 https://github.com/etcd-io/etcd.git arm71Update .bashrc with
Source that, then, use a script like below to install Go
etcd build is actually the same - now that we have our Go env vars in place. $ git clone -b v3.4.16 https://github.com/etcd-io/etcd.git Do whatever you want with the binaries - move them to /usr/bin, /usr/local/bin, leave them as is and add to path - whatever. The really odd thing is that if you do this wrong, you get this maddening error: Anyway - it's a weird case - hope I help one person one day. |
Hi,
I have installed the etcd3.3.12 (etcd-v3.3.12-linux-arm64.tar.gz)on the Intranet.
I'm trying to start the etcd.service but the Job for etcd.service failed and I have seen “journalctl -xe” for details, and then I got:
etcd[20836]: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=arm64 set.
systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Etcd Server.
Then, I have added the variable by export ETCD_UNSUPPORTED_ARCH=arm64 and I've got the same result.
When I enter the command etcd & , I got this:
2019-04-25 19:46:55.131947 W | etcdmain: running etcd on unsupported architecture "arm64" since ETCD_UNSUPPORTED_ARCH is set
2019-04-25 19:46:55.132284 I | etcdmain: etcd Version: 3.3.12
2019-04-25 19:46:55.132298 I | etcdmain: Git SHA: d57e8b8
2019-04-25 19:46:55.132308 I | etcdmain: Go Version: go1.10.8
2019-04-25 19:46:55.132318 I | etcdmain: Go OS/Arch: linux/arm64
How can I solve it?
May I consider that my operating system is incompatible with etcd3.3.12?
Thanks very much
The text was updated successfully, but these errors were encountered: