You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to allow passing through of nspawn's switches to debspawn?
background
debspawn login allows interaction with the container, f.e. administrative stuff using the --persistent switch. But login doesn't allow to mount a directory from the host. Also, I wasn't able to store any data to the host. Writing to /srv/build inside the container didn't create a file anywhere on the host.
workaround
A hack would be to use debspawn run --build-dir=/opt/here buster /usr/bin/env bash.
benefits
The user could even mount a directory as read-only if it shouldn't be modified during the session.
The text was updated successfully, but these errors were encountered:
I could imagine adding a switch to mount arbitrary directory from outside the container into the container to the login command and possibly run command only. When something is built using build I want the built to be affected by the least amount of parameters from the outside that is possible - when something is built with debspawn, the result should be the same no matter where it was built.
Allowing arbitrary nspawn commands to be forwarded falls into the same category. When adding something, I'd much rather add features selectively.
That being said, I think adding an option to mount arbitrary stuff for login and run is fine, patches welcome! (I'll get to implementing it eventually as time permits, but a dedicated PR is always faster)
Another use case for external mounts in particular: I was attempting to be clever and use --extra-source-lines to point to a local repo, not realizing that it would (obviously) be interpreting the file:/// path from inside the container.
tl;dr
Would it be possible to allow passing through of nspawn's switches to debspawn?
background
debspawn login
allows interaction with the container, f.e. administrative stuff using the--persistent
switch. Butlogin
doesn't allow to mount a directory from the host. Also, I wasn't able to store any data to the host. Writing to/srv/build
inside the container didn't create a file anywhere on the host.workaround
A hack would be to use
debspawn run --build-dir=/opt/here buster /usr/bin/env bash
.benefits
The user could even mount a directory as read-only if it shouldn't be modified during the session.
The text was updated successfully, but these errors were encountered: