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
Describe the bug
When I try to start the container with systemd-nspawn -M debian-custom -D /data/custom/machines/debian-custom I get the error Failed to allocate a pty: No such file or directory
To Reproduce
Steps to reproduce the behavior:
Run the command above.
UDM Information
UXG Lite 3.1.16
Additional context
When I run it with systemd-nspawn -M debian-custom -D /data/custom/machines/debian-custom -P it continues. I'm not sure what pipe mode means and if this is a good thing to do. It failes when creating a service later on, so not even a real solution.
When doing some troubleshooting I see i probably failes in the procedure openpt_allocate. But from the I'm totally lost. On Windows I can run processmon.exe to troubleshoot, on Linux I don't know my way.
The text was updated successfully, but these errors were encountered:
Describe the bug
When I try to start the container with
systemd-nspawn -M debian-custom -D /data/custom/machines/debian-custom
I get the error Failed to allocate a pty: No such file or directoryTo Reproduce
Steps to reproduce the behavior:
UDM Information
Additional context
When I run it with
systemd-nspawn -M debian-custom -D /data/custom/machines/debian-custom -P
it continues. I'm not sure what pipe mode means and if this is a good thing to do. It failes when creating a service later on, so not even a real solution.When doing some troubleshooting I see i probably failes in the procedure openpt_allocate. But from the I'm totally lost. On Windows I can run processmon.exe to troubleshoot, on Linux I don't know my way.
The text was updated successfully, but these errors were encountered: