![]() I have enough resources allocated to the container so that should not be a bottleneck.Īny suggestions on how to proceed in determining the root cause would be much welcomed )įirstly, apologies for slow response. But the fact that I have this time around whilst still running into this wall suggests there is mroe wrong with my setup than obvious at first glance. I have been troubled by something similar in the past and then the conclusion was to enable nesting. │ was given a height or width parameter that is too big │ Sometimes, the reason is simply that dialog │ │ (which was passed to it as the DIALOG_ERROR environment │ │ error: the dialog-like program exited with status 3 │ │ dialog.DialogError: dialog-like terminated due to an │ │ in _wait_for_program_termination raise DialogError( │ │ "/usr/lib/python3/dist-packages/dialog.py", line 1430, │ │ self._wait_for_program_termination(child_pid, File │ │ "/usr/lib/python3/dist-packages/dialog.py", line 1484, │ ![]() │ self._handle_program_exit(child_pid, File │ │ "/usr/lib/python3/dist-packages/dialog.py", line 1518, │ │ in _widget_with_string_output code, output = │ │ "/usr/lib/python3/dist-packages/dialog.py", line 1719, │ │ self._widget_with_string_output( File │ │ "/usr/lib/python3/dist-packages/dialog.py", line 3130, │ │ per.py", line 82, in wrapper retcode = method(" │ │ "/usr/lib/python3/dist-packages/libinithooks/dialog_wrap │ Traceback (most recent call last): File │ Only hitting backspace will show the following The first init sequence starts and I am asked to enter a password for adminer.Īs soon as I hit enter after typing the password the screen freezes. When logging in for the first time using the console feature of the procmox GUI. Pve-manager/7.4-3/9002ab8a (running kernel: 5.15.104-1-pve)Ĭontainer is unprivilidged and has nesting enabled both at creation time and runtime.
0 Comments
Leave a Reply. |