Skip to content
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: fix systemd unit files #120019

Merged
merged 2 commits into from Apr 26, 2021
Merged

Conversation

gfrascadorio
Copy link
Member

@gfrascadorio gfrascadorio commented Apr 21, 2021

Add missing docker.socket file and patch ExecStart in docker.service
so these units are useful on non-nixos systems using systemd.
(issue #70407)

Motivation for this change

Re-discovery of open issue #70407 - which describes missing and unpatched systemd unit files for docker.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions (Ubuntu 20.04)
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date (gf: didn't find any)
  • Fits CONTRIBUTING.md.

Add missing docker.socket file and patch ExecStart in docker.service
so these units are useful on non-nixos systems using systemd.
(issue NixOS#70407)
@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/docker-packages-systemd-unit-files-dont-work-on-ubuntu/12160/4

@gfrascadorio
Copy link
Member Author

I see that one of the checks failed "This PR does not cleanly list package outputs after merging."
Can someone help me understand what that means and how to fix it?

@SuperSandro2000
Copy link
Member

Open the Details link next to it.

I think what is happening is that on non linux Docker can't be evaluated because buildGoPackage is empty and does not goPackagePath.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants