makefu changed the topic of #nixos-wiki to: Welcome to the *unofficial* nixos wiki | https://nixos.wiki | chat logs: https://logs.nix.samueldr.com/nixos-wiki/
orivej has quit [Ping timeout: 248 seconds]
orivej has joined #nixos-wiki
orivej has quit [Ping timeout: 240 seconds]
<Profpatsch> Mic92: How do you mean, “miss the nixos parts”?
<Mic92> Profpatsch: system configuration.
<Mic92> the stuff added by nixos/
<Profpatsch> You mean you’d like to have them?
<Mic92> Yes. Otherwise I would have to reinvent the wheel.
<Profpatsch> I’d like to keep the closures as small as possible.
<Profpatsch> Which is pretty hard with nixos
<Profpatsch> You get shit you’d never need.
<Mic92> I want to use all packages with the host.
<Profpatsch> All packages?
<Mic92> Then it does not make much of a difference
<Profpatsch> Which host?
<Mic92> the host the container is running on
<Profpatsch> I’m talking about docker containers, not VMs.
<Mic92> The container should only see its closure
<Mic92> This is possible with bind mounts
<Profpatsch> So not Nixops, there is no nix inside the container.
<Mic92> Yes.
<Profpatsch> Still not sure what you mean.
<Mic92> something like this: https://github.com/Mic92/nix2aci#thin-acis
<Profpatsch> Yeah, you /can/ mount stuff into containers, but normally that doesn’t work very well with e.g. docker
<Profpatsch> Additionally, you can’t run systemd inside of containers.
<Mic92> you can
<Mic92> I do that for years
<Profpatsch> No, not inside of unpriviledged containers.
<Mic92> I have unprivileged lxc containers running with systemd.
<Profpatsch> That’s lxc
<Profpatsch> Not docker
<Mic92> Yes.
<Profpatsch> Yeah, different.
<Mic92> you can do the same thing with docker too.
<Profpatsch> Nope. Not that I know of.
<Profpatsch> Anyway, you’d still need to include systemd into the closure of each container.
<Profpatsch> Which is a waste if you want to really separate stuff.
<Mic92> This is not a problem for me, since it is running on the host as well
<Profpatsch> It’s still going to take space.
<Profpatsch> Or are you bindmounting in the whole store?
<Mic92> no the space is already taken on the host, binaries are shared in memory
<Profpatsch> wat
<Profpatsch> I’m not sure what you are talking about, really.
<Mic92> I want bind mount parts of the nix store.
<Profpatsch> Yeah, but then it’s not a container.
<Profpatsch> Because it can’t function outside of a nixos.
<Mic92> why that?
<andi-> mic is talking about containers using nixos (e.g. sharing (partially) the /nix/store) Profpatsch is trying to create docker images (to run on any docker host)
<Profpatsch> Right.
<Profpatsch> I mean then you have a glorified separation layer.
<Profpatsch> I’m not even sure why’d you want that and not just use nspawn services directly from nixos?
<Profpatsch> The separation should be about the same.
<Mic92> Is not that what containers are about? Docker is pretty waste a lot of disk space.
<Mic92> I want to base it on nspawn, but I have some road blocks to make it unprivileged.
<Profpatsch> There’s a lot of different technologies at work here, combined in every way you can think about.
<Profpatsch> So if someone says “containers”, you can’t know what they are talking about before they describe their stack.
<Profpatsch> Anyway, Community Overview seems a bit too general.
* andi- is always a bit pissed about the assumption of most people that containers always equals docker...
<Profpatsch> We’d like to use the Wiki as a link collection for people interested in building self-sufficient OCI images.
<Mic92> you mean moby ;)
<Mic92> Just make an article about OCI.
<Profpatsch> Yeah, nah, it’s not going to be of article quality.
orivej has joined #nixos-wiki
<Profpatsch> And definitely not about what already exists in nixpkgs, but for organizing what to build for nixpkgs.
<Profpatsch> So not so much documentation.
<Profpatsch> That’s why I’d call it working group, to organize stuff people are building and make it discoverable, also to comment.
<samueldr> Profpatsch: depending on how it looks like, we may move it into an implementation notes namespace for nix/nixos developers; if I understand correctly that's what you want to do, right?
<Profpatsch> A bit like a talk page on Wikipedia.
<samueldr> (there is no such namespace right now, but in the past the idea was raised)
<Profpatsch> Hm, not really.
<samueldr> the archlinux wiki has a namespace for "archlinux developers"
<Profpatsch> Just a space for a working group to organize.
<Profpatsch> Like a Project on Wikipedia.
<samueldr> so I think I understood
<samueldr> the idea mainly being that in the main namespace end-user articles are present
<Profpatsch> Maybe use the namespace WorkingGroups:OCIContainers
orivej has quit [Ping timeout: 256 seconds]
srid`` has quit [Quit: The Lounge - https://thelounge.github.io]
srid_ii has quit [Remote host closed the connection]
orivej has joined #nixos-wiki
ixxie has joined #nixos-wiki
<Reaktor|krebs> ixxie: right now I'm updating my packages page manually, ping me if it's too out of date for your use, I'll look into automatic deploys later -- samueldr!~samueldr@unaffiliated/samueldr, Sat Feb 3 15:46:19 CET 2018
<ixxie> reaktor help
<ixxie> Reaktor|krebs: help
<Reaktor|krebs> I'm famous
<ixxie> samueldr: are you in?
<ixxie> Reaktor|krebs tell samueldr well I am trying to see if my latest PRs are in unstable
<Reaktor|krebs> I'm famous
<ixxie> fadenb: how do you use this bot again?
<samueldr> ixxie: no need to "tell" Reaktor|krebs since I'm always here \o/
<Reaktor|krebs> I'm famous
<samueldr> but you had it
<fadenb> Reaktor|krebs: tell ixxie use a colon after the bot name. perhaps?
<Reaktor|krebs> Consider it noted.
<ixxie> thanks fadenb xD
<ixxie> samueldr: I had what?
<samueldr> the use, but I might have been wrong in the end
<samueldr> * how to use the bot
<ixxie> colon was missing, thas all
<samueldr> but yeah, as long as I'm in the channel, the bot will simply say it directly, so just ask me
<samueldr> and for your query, yeah, that's what I understood, I can update it if you ask, it's really easy for me, it's simply not automated
<ixxie> yeah its cool, clever just gave me a trick about doing tab completition in nix-repl
<ixxie> also soon nix search will be in the house
<ixxie> and then hopefully my little droplet can have a decent cli search for packages
<ixxie> samueldr: that said, your search would be very useful if it was continuously updated, because there isn't a web search tracking unstable
<samueldr> when I'm done with a PR I'm working on, I'm re-working that package search to open a PR on the nixos website
<samueldr> this was a demo of something I wanted to upstream, but the way it's made right now wouldn't pass (maybe)
<samueldr> at least, I'm not okay with how I did it
<samueldr> the PR I'm working on btw, if curiout https://github.com/NixOS/nixpkgs/pull/33686
<samueldr> though, looks like I haven't sent the update I was writing yesterday
<ixxie> samueldr: oooh cool
<ixxie> samueldr: that is awesome
<ixxie> although I think with a white background it would look even better
<ixxie> I should look into that logo revamp I have been working on this week
<ixxie> maybe we can combine this with the RFC for the new style
<samueldr> anyway, as I described, the big thing with the PR is re-working the iso configuration so that it is now possible
<samueldr> I may even do a more subdued revision until there is "real" graphic design done
<ixxie> right
<ixxie> of course
<ixxie> exciting
<ixxie> what other options does this bring? It looks fancier
<ixxie> aargh I gtg, maybe you can tell me more next time ^^
<samueldr> easier for the eyes on hidpi displays
<ixxie> but the menus seem to have a bunch of options I never normally see in the bootloader
<ixxie> anyway, good night
ixxie has quit [Quit: Lost terminal]
the_real_plumps_ has quit [Remote host closed the connection]
the_real_plumps has joined #nixos-wiki