Skip to content
#

nixos

Here are 417 public repositories matching this topic...

nixpkgs
nixery
coderfromhere
coderfromhere commented Feb 24, 2020

Hi!

The current nixery-based containers lack clarity around ldconfig specifics in Nix, which breaks software tooling expectations, that are usually met within conventional Linux distributions.

For instance, consider the Haskell Stack

[nix-shell:~]$ docker pull nixery.dev/shell/which/stack
Using default tag: latest
latest: Pulling from shell/which/stack
30c2bb75530a: Already exis
jhillyerd
jhillyerd commented Apr 24, 2020

I don't find mention of how to install plugins in the README or the docs linked from there.

Assuming most new nixops users are going to want to try nixops with libvirtd or VirtualBox, this is a significant adoption blocker.

alexanderkjeldaas
alexanderkjeldaas commented Apr 19, 2018

I'd like to understand how this compares to:

https://nixos.wiki/wiki/Installing_from_Linux

Also, how this compares to downloading a NixOS ISO and starting some sort of installation procedure from that ISO, if that's different from the link above.

A section in the README that says something about what this does not do, and what it improve on, and what it does (the latter is somewhat desc

johanot
johanot commented Feb 18, 2019

It should be possible to supply a full shell script to morph to be executed on a/multiple remote host(s).

Something along the lines of morph exec --script foobar.sh ./hostgroups/k8s.nix

The supplied script would be uploaded to the remote hosts as tempfiles and executed like so: bash /tmp/xXya81.foobar.sh

If the --script flag is provided, the command argument should either be:

  • omi
stites
stites commented Jun 12, 2016

...Once you have the results, type the numbers of the packages to install.

Bonus: if you enter the letter 's' at the beginning of the package numbers list, a nix-shell will be started with those packages instead.

Cool feature! I arrived here for a separate issue, found this, and was compelled to suggest that you mention this in the non-existent man-page, help summary, or with nox dur

arion
roberth
roberth commented Jan 7, 2019

The goal is to help users who are defining their images via dockerTools.

  • useHostStore = true -> avoid docker load
  • useHostStore = false -> do use docker load, for more production-like testing

Unanswered question: when using the host store, do we need to build a custom base image to get the attributes right, or can all the relevant attributes be set at the docker compose service l

colemickens
colemickens commented Feb 25, 2020

From IRC this morning, #nixos:

15:36 <Taneb> dvn: can you share what you've written?
15:37 <dvn> Taneb: see -> https://github.com/colemickens/nixpkgs-wayland#usage-nixos-unstable
15:37 <{^_^}> [nixpkgs] @clkamp opened pull request #81031 → coreboot-utils: 4.10 -> 4.11 → https://git.io/JvuvJ
15:37 <dvn> Taneb: i just copied that codeblock there
15:38 <dvn> put it in ~/.config/nixpkgs/over
rissson
rissson commented Jan 22, 2020

Steps taken :

  • Install ArchLinux and create a user
  • Install Nix (multi-user installation)
  • Enable nix-daemon.service
  • Install nix
  • Do something like that `RELEASE=release-19-09 NIX_PATH="nixpkgs=$(nix-build --no-out-link "/home/risson/code/shabka" -A "external.nixpkgs.release-19-09.path"):shabka=/home/risson/code/shabka" nix-shell -I "home-manager=$(nix-build --no-out-link "/home/ris
zielmicha
zielmicha commented Jan 21, 2018

In faq.rst there is a section about binary caches:

How do I add a new binary cache?
Using Nix:
$ echo "trusted-binary-caches = https://hydra.snabb.co" >> /etc/nix/nix.conf

This doesn't seem correct, because single-user Nix doesn't use /etc/nix by default (only when NIX_CONF_DIR environment variable is set to /etc/nix, tested on 1.11.15) - I'm not sure what directory it uses then.

stevenroose
stevenroose commented Apr 4, 2020

The installation instructions use nixops for installation and deployment of the machine.

I'm trying to use the modules without using nixops. And I'm having issues with the secrets file.

Failed to start bitcoind.service: Unit nix-bitcoin-secrets.target not found.
the following new units were started: electrs.service
warning: the following units failed: liquidd.service, nginx.service

Improve this page

Add a description, image, and links to the nixos topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the nixos topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.