como consertar o sistema de arquivos de um contêiner LXC

1

Este contêiner não inicia mais com essas mensagens de erro:

# lxc-start -n deb7 -F
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Cleaning up temporary files... /tmp.
Mount point '/proc/sysrq-trigger' does not exist. Skipping mount. ... (warning).
Mount point '/dev/console' does not exist. Skipping mount. ... (warning).
Mount point '/dev/ptmx' does not exist. Skipping mount. ... (warning).
Mount point '/dev/tty1' does not exist. Skipping mount. ... (warning).
Mount point '/dev/tty2' does not exist. Skipping mount. ... (warning).
Mount point '/dev/tty3' does not exist. Skipping mount. ... (warning).
Mount point '/dev/tty4' does not exist. Skipping mount. ... (warning).
Activating lvm and md swap...done.
Checking file systems...Segmentation fault (core dumped)
failed (code 139).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning).
Give root password for maintenance
(or type Control-D to continue): 
Segmentation fault (core dumped)
Attempt to start maintenance shell failed. Continuing with system boot in 5 seconds. ... failed!

configuração:

lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:61:07

lxc.rootfs.path = dir:/var/lib/lxc/deb7/rootfs

# Common configuration
lxc.include = /usr/share/lxc/config/debian.common.conf

# Container specific configuration
lxc.tty.max = 4
lxc.uts.name = deb7
lxc.arch = amd64
lxc.pty.max = 1024

Outros contêineres na mesma máquina são bons, apenas este não é iniciado.

Obrigado.

    
por Matthieu 09.02.2018 / 15:21

1 resposta

1

Eu tenho exatamente o mesmo problema com um contêiner wheezy debian em minha máquina host arch linux. Também não foi possível criar um novo contêiner wheezy debian (outras versões debian funcionaram). Depois de mudar do kernel 4.15.2-2 para 4.14.18-1-lts o problema desapareceu.

ATUALIZAÇÃO: abra / etc / default / grub e adicione vsyscall = emulate aos parâmetros GRUB_CMDLINE_LINUX_DEFAULT, então execute grub-mkconfig -o /boot/grub/grub.cfg ou update-grub no ubuntu, restart, party.

    
por 15.02.2018 / 10:09

Tags