-
Notifications
You must be signed in to change notification settings - Fork 24
Brittle hostname makes fleek apply
fail with Error: system not found
#324
Comments
fleek apply
fail
So there would be some inconsistency somewhere. I suppose It would help if instead of printing
we got e.g.
I wonder if this new employer would allow me to take some time to try contributing a patch for this? I'm no regular go and nix developer, though, and obviously, making the hostname resolution more consistent, or standardizing based on serial number might be better (as suggested in #149; not sure I like the idea of this, though, since it's not readable and a bit creepy). Furthermore, what should I do now? I could copy-paste or rename stuff around in my dotfiles but I'm trying to reach for an easier way to recuperate so that my less tech-savvy colleagues would feel OK with us using fleek. I hoped |
A way to circumvent the issue is by abusing the ephemeral systems feature: export FLEEK_HOST_OVERRIDE=admins-MacBook-Pro.local
fleek apply But still, having colleagues export an envar for this might be a bit too much. |
Reproduced the issue on a new mac. If I remember well, here are the results of running
|
fleek apply
failfleek apply
fail with Error: system not found
Documented here https://getfleek.dev/docs/troubleshooting/system_not_found It happened to me when I switched to a different network. |
The same new mac as on Nov 20 above echoes a third different hostname today:
If I toggle off my network adapter, This all goes to confirm that My current strategy is to duplicate the systems in Update: this symlinking strategy is only good when my mac steals the |
Going home and to work it breaks as hostname is dependent on the network and I would have to make the change every day, potentially multiple times a day. Wouldn't consider this a fix: https://getfleek.dev/docs/troubleshooting/system_not_found |
Describe the bug
fleek apply
worked fine yesterday after I installed Fleek and every time I called it in the next hour or so.Today:
To Reproduce
Put the Mac to sleep and let it wake? Not sure.
Expected behavior
A stable way to identify the host would fix this without having us editing our
.fleek.yml
.Environment
Additional context
![image](https://private-user-images.githubusercontent.com/28544/283474996-2a280e47-5888-489d-a102-4b5a5e93569e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU0NjM5NTIsIm5iZiI6MTcyNTQ2MzY1MiwicGF0aCI6Ii8yODU0NC8yODM0NzQ5OTYtMmEyODBlNDctNTg4OC00ODlkLWExMDItNGI1YTVlOTM1NjllLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA0VDE1MjczMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZiZmQwZWY1NTY4ZjNmODU2ZTFmYTI2YzkyMjdmOGY2ODllZmM0OWE5NDhkMzdhODI2NGZkMTU1N2I0NjkyNjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.FMb2j___HmVH5TMJpKRk7mY4JJ8nHQ68EjS8RXQue00)
I didn't change the Mac's hostname. Here's what it was yesterday, and still is today:
#149 is similar in some ways.
The text was updated successfully, but these errors were encountered: