+7 (495) 320-70-49
- Назад
- Телефоны
- +7 (495) 320-70-49
- Заказать звонок
info@proxmox.su
Москва, Бакунинская улица, 69с1
Пн-Пт: 09-00 до 18-00
Сб-Вс: выходной

Новый привилегированный контейнер без консоли., Proxmox Виртуальная Среда

zamadatix

Guest

27.09.2024 17:48:00

На Proxmox VE 8.2.7 я скачал последние контейнеры Ubuntu и Arch: archlinux-base_20240911-1_amd64.tar.zst ubuntu-24.04-standard_24.04-2_amd64.tar.zst и попробовал развернуть их, не ставя галочку "Unprivileged container". При запуске контейнеров и переходе на вкладку Console консоль никогда не загружается. Установка IP-адреса не пингуется, будто контейнер не завершает запуск. Наблюдаю такое же поведение на нескольких хостах. Если развернуть контейнер, оставив галочку "Unprivileged container" отмеченной, все работает нормально.

Crogdor

Guest

09.11.2024 04:10:00

Поднимаю этот вопрос — столкнулся с той же проблемой на 8.2.7. Могу создавать контейнеры, привилегированные или нет, но консоль подключается только к непривилегированным. Если зайти на хост Proxmox через SSH и использовать `pct` для входа в контейнер, можно увидеть следующие ошибки:

```
root@proxmox-4:/etc/pve/lxc# pct start 131
root@proxmox-4:/etc/pve/lxc# pct enter 131
root@canbus:/# journalctl -p err -b 0
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Nov 09 03:07:38 canbus (networkd)[93]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (networkd)[99]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (networkd)[105]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (tmpfiles)[118]: systemd-tmpfiles-setup.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
Nov 09 03:07:38 canbus (resolved)[135]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus (networkd)[130]: systemd-networkd.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
Nov 09 03:07:38 canbus (resolved)[149]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus (resolved)[165]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus (resolved)[176]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus (resolved)[188]: systemd-resolved.service: Failed to set up credentials: Protocol error
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Nov 09 03:07:38 canbus systemd[1]: Failed to start apparmor.service - Load AppArmor profiles.
Nov 09 03:07:38 canbus (d-logind)[244]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[284]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[296]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[314]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:38 canbus (d-logind)[332]: systemd-logind.service: Failed to set up mount namespacing: Permission denied
Nov 09 03:07:38 canbus systemd[1]: Failed to start systemd-logind.service - User Login Management.
Nov 09 03:07:39 canbus (agetty)[452]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[451]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[457]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[456]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[460]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[461]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[463]: container-getty@1.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[465]: container-getty@2.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus systemd[1]: Failed to start container-getty@1.service - Container Getty on /dev/tty1.
Nov 09 03:07:39 canbus systemd[1]: Failed to start container-getty@2.service - Container Getty on /dev/tty2.
Nov 09 03:07:39 canbus (agetty)[468]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[470]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[472]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:39 canbus (agetty)[474]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:40 canbus (agetty)[474]: console-getty.service: Failed to set up credentials: Protocol error
Nov 09 03:07:40 canbus systemd[1]: Failed to start console-getty.service - Console Getty.
```

DougW Guest	#3 0 22.11.2024 05:57:00 У меня та же проблема с образом ubuntu-24.10-standard_24.10-1_amd64 прямо из pveam.

wiggyware

Guest

02.01.2025 20:04:00

Для тех, у кого тоже возникла такая проблема: нужно включить "nesting" в настройках контейнера. Непонятно, как включить его для привилегированного контейнера при создании. Придётся отредактировать настройки контейнера и включить там.

Спасибо papatikka за их пост здесь: https://forum.proxmox.com/threads/lxc-mantic-minotaur-upgraded-from-lunar-systemctl-degraded.129842/

vicmarto Guest	#5 0 03.03.2025 05:45:00 У меня та же проблема, использую Proxmox 8.3.4 с ubuntu-24.04-standard_24.04-2_amd64: нужно включить Nesting. А вот debian-12-standard_12.7-1_amd64 работает с Nesting выключенным.

dodgerbluee Guest	#6 0 30.03.2025 21:23:00 У меня заработало, wiggyhero

Читают тему

Главная Каталог 0 Корзина 0 Избранные Кабинет 0 Сравнение Акции Контакты Услуги Бренды Отзывы Компания Лицензии Документы Реквизиты Поиск Блог Обзоры