srd424

It would be great if `balena deploy` could take a `.local` hostname instead of a fleet name, like `balena push` does.

I haven't looked at this in any detail, but a while ago I had problems with network config confusion in nspawn (see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1841378) - they seemed to be fixed by...

Skimming this it sounds like at least some of the problems are caused by using user namespacing? If you read the links from https://github.com/systemd/systemd/pull/9483#issuecomment-449602341 it seems the kernel has started...

Binding devices nodes in doesn't seem to work any more, possibly a user namespace specific issue. Unless that's another manifestation of #20989?

Some quick tests with 250 to refresh my memory - with userns on, bind mounted /dev nodes end up owned by nobody:nogroup so not ~~necessarily~~ writable; trying to add `:idmap`...

Long-term, image tags / labels might be the most flexible thing? For now I'd love the ability to nest albums, or at least a more compact list of albums to...

It's been reported to me that the following LD_PRELOAD hack works around this problem successfully, as a stop-gap solution: ``` #define _GNU_SOURCE #include #include // gcc -Wall -fPIC -shared -o...

I'm really struggling to follow the code, but I wonder if we need to store `EtcFile`s (or something very similar) in the `FileTree`s?

The following seems to more or less work, not sure why I need to use `image.command` instead of `service.command`. Perhaps in the "non-full NixOS" case `service.command` could be automatically written...

Oh, this is simpler: ``` { pkgs, ... }: { project.name = "webapp"; services = { webserver = { image.enableRecommendedContents = true; # service.useHostStore = true; image.command = [ "sh"...