-
Notifications
You must be signed in to change notification settings - Fork 107
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
Ob deploy push fails with exit code 1 #6
Comments
@SebastianCallh Could you show the output of |
Hi @srid! Great idea, apparently it tries to fetch from an url that gives 404. Sorry about the formatting, the output is below Starting Obelisk </nix/store/s200msjpipi4jpyv2xkas35dsb101s9m-obelisk-command-0.1/bin/ob> args=Args {_args_noHandOffPassed = False, _args_verbose = True, _args_command = ObCommand_Deploy DeployCommand_Push} noSpinner=False logging-level=Debug trying https://github.com/obsidiansystems/obelisk-https/archive/5bc5cd81b669a0ea1b4415a1be8fd8c5a0680f0b.tar.gz |
@SebastianCallh just made that package public which should resolve the 404 |
@luigy Yeah it ran past that step now but after a while it got stuck on a permission denied. This shouldn't need sudo, right? I don't really understand what it's doing in the /boot folder.
|
@SebastianCallh Thanks for pressing through. I sadly have never seen this before. What system are you running on? Ubuntu? |
@3noch No problem! That's right, Ubuntu 16.04. I have put the entire output from |
@3noch I see now that the instance is in fact running NixOS 18.03 and not NixOS 17.09. Whoups. That could be it? I will try with an instance with the proper version later today and get back to you. |
@3noch That was not the issue. The error remains. |
Looks like NixOS/nixpkgs#29448 |
@alexfmpe You're totally right. How do we proceed with this? |
@SebastianCallh Looks like that issue has a workaround in the comments (but it's ugly). This is a nasty bug with nixpkgs on Ubuntu. I have another possible workaround coming that uses docker to run the actual deployment builds. We need this for macOS but I think it could probably be a workaround for this issue as well. |
@3noch Yeah I saw it. Unfortunately I don't trust myself enough to restore the boot folder after every build. This is quite the bummer |
@SebastianCallh It may only need to be done once (populate the cache and be done) but I don't know for certain. I wouldn't want to do that myself either... Let's hope that my virtualized remote builder helps here until nixpkgs gets things together. |
@3noch That's a possibility but I'd rather not. Looking forward to it! Shoot me a message if I can assist with testing or anything. |
@3noch Yeah, that workaround is quite a bit more dangerous than people can
reasonably do. Can we try to sort this out upstream?
…On Sat, May 26, 2018, 07:11 Sebastian Callh ***@***.***> wrote:
@3noch <https://github.com/3noch> That's a possibility but I'd rather
not. Looking forward to it! Shoot me a message if I can assist with testing
or anything.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABGlYHMyiegglavRrEQlgRStU9W6tg1gks5t2HOagaJpZM4UMz5l>
.
|
@SebastianCallh Can you check whether /etc/nix/nix.conf says |
@ryantrinkle It did not have Are there any consequences to be aware of when running in sandbox mode? |
@SebastianCallh Awesome! I'm glad that fixed it; nix stuff really should not be reading outside of its own area. The consequences of using sandboxing are mostly that it is slightly slower (on the order of 30ms per derivation, if I recall correctly), and that it is more robust. On NixOS, sandboxing is on by default. On some OSes, creating/entering a sandbox may require elevated permissions, but that doesn't seem to have been the case for you. I've created an issue to help with this: #28 |
@ryantrinkle Awesome! I haven't used |
After having installed Obelisk on Ubuntu 16.04 by following the instructions in the readme (installing Obelisk in the nix-env, and using hub) and trying to deploy the example app(also following the readme) the command
ob deploy push
fails with the following error message.The content of the ./src folder in the myapp-deploy have not been edited by hand and consists of the default.nix file
the github.json file
and the .attr-cache folder which is empty.
The text was updated successfully, but these errors were encountered: