-
Notifications
You must be signed in to change notification settings - Fork 108
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
Docker builds stopped working after update #209
Comments
Not related to the root cause for above, but stability of a devos installed application (docker). I'm not sure if devos wants to guarantee sane defaults for something like docker or not, but I also ran into "too many files open" and ended up finding this yet to be merged PR that addresses that issue: I think devos relies on nixpkgs to set these defaults unless it's something egregious? Actually, I don't know if core even has docker anymore or if it's a goal for community to have sane defaults. |
I don't think it is a bad idea to preempt those changes in the In the case those are specific PRs from upstream that we might want to pull in to make devos generally more usable, we should probably defer to |
Docker is obviously huge for hackers of all stripes, so ensuring simple usage is certainly a good idea in general. Perhaps a nice test suite to ensure docker is working correctly would be in order, to ensure PRs don't break it. |
Fix: NixOS/nixpkgs#126777 |
Nowadays most applications require a good amount of inotify watches, so raise our default to what other distros do. If kernel supports it enable dynamic setting. fixes NixOS#36214, NixOS#65001 (re-fix) - NixOS/nixops#890 - divnix/digga#209 replaces: NixOS#112472
This is beeing tracked by NixOS/nixpkgs#36214 (comment) (and closed once resolved) (edit @blaggacao)
This might not even belong here, but in the off chance that rebuilds or reactivation don't fully work correctly and devos does anything special I'm posting it in case.
I updated my dependencies here:
codygman@eedf122
I went to build a docker container I'd built recently got a failure, so I tried getting a shell in the base container and calling the failing command:
After a
flk work-tower switch
at this commit I tried the above again and got the issue.Upon rebooting though and still at that commit, this happens:
It works.
I wouldn't be surprised if maybe this is an issue similar to this one about socket activation and the correct course of action being creating an issue upstream.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: