Skip to content
Discussion options

You must be logged in to vote

We still need to point to a rootfs for the base of the container, even if it's just an empty directory. That's effectively what we're doing on darwin/windows.

I'm not familiar with nix, so I'm lost on how this practically works. If we create an empty rootfs:

.
├── rootfs/ #it's empty
└── metadata.json

How do you do anything with this? You can't exec anything in this container since it's empty. I guess you could pull in anything you need via task inputs? The running container's filesystem would then look like:

/ 
└── tmp/
    └── build/
        └── abc123/
            ├── input1
            ├── input2
            └── input3
# nothing else in the container's filesystem...

I just realized th…

Replies: 3 comments 21 replies

Comment options

You must be logged in to vote
10 replies
@lenianiva
Comment options

@lenianiva
Comment options

@dgengtek
Comment options

@lenianiva
Comment options

@dgengtek
Comment options

Answer selected by lenianiva
Comment options

You must be logged in to vote
2 replies
@taylorsilva
Comment options

@dgengtek
Comment options

Comment options

You must be logged in to vote
9 replies
@lenianiva
Comment options

@dgengtek
Comment options

@lenianiva
Comment options

@taylorsilva
Comment options

@bcersows
Comment options

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