-
Notifications
You must be signed in to change notification settings - Fork 60
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
Check target architecture before deploying #168
Comments
So the root cause remains: the |
So I found the root cause for the issue: morph does not check for whether the architecture for which the configuration was built is correct. The configuration will then contain a shebang to a wrong binary, which will lead to failure. A preliminary check would catch this gracefully. To the error message, this is a bug in Bash (actually, they say it's not because it's specified in POSIX, so one could call it a bug in POSIX): If the execution of a shebang fails, Bash will try to interpret the file directly. Of course this makes no sense, and since our file is a perl script we thus get the |
Do you have any good tips for recovering a host that has been morphed with the wrong architecture? |
No, I was fortunate enough that the activation script was in Perl and thus failed before it could do any harm. You may try executing the activation script in emulation mode (with |
I copied over the activation script from a previous generation and that made it happy to deploy again. |
Continuation of #64 because I just ran into this again. Error message:
The script in question:
The machine is a Raspberry Pi 4 (
Linux 5.10.61 #1-NixOS SMP aarch64 GNU/Linux
)The text was updated successfully, but these errors were encountered: