Closed bjornfor closed 2 years ago
I can't reproduce this, neither locally, nor by running your example in the reference VM (via nix run github:erikarvstedt/extra-container#vm
).
What's your system environment? Do you use NixOS? If yes, what's your NixOS version and system.stateVersion
?
This is on Ubuntu 18.04. Thanks for checking. I'll try to debug this from my side then.
With set -x
debugging I found that it was PEBKAC:
extra-container
.extra-container
outside of the shell.nix file on the remote machine -- big mistake -- inadvertantly using an old version!)extra-container destroy
.So yeah... completely PEBKAC!
Sorry for the noise and thank you for creating extra-container! I'm really exited to have access to declarative NixOS on impure Ubuntu!
Either I'm misunderstanding the purpose of
destroy
or it's a bug :-) (I thought it'd stop the containers and wipe/var/lib/nixos-containers/NAME
.)Using latest extra-container version (0.10).