Is there any way to fire up a pid-1-systemd isntance inside a debspawn container, so that the container could have an IP address and run itsI am not familiar with debspawn, but looks like this should help:
own sshd? Or is there any way to get a login prompt from an already
running debspawn container?
Hallo,
debspawn is extremely handy if one just wants a container to quickly try stuff or to build a package in a clean environment. I especially like
that zero infrastructure is needed: We already have systemd and that's
all whats needed to fire up an nspawn container.
But sometimes, one wants more than that, for example two shells in the
same container. That's something that debspawn seems to be unable to do.
Is there any way to fire up a pid-1-systemd isntance inside a debspawn container, so that the container could have an IP address and run its
own sshd? Or is there any way to get a login prompt from an already
running debspawn container?
What magic have other people built around debspawn? Or is everybody
using a fully-fledged docker for all non-trivial things?
Greetings
Marc
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 145:46:11 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,685 |