search

whiskerz007 / proxmox_hassio_lxc

MIT License
208 stars 83 forks source link

ifelse: fatal: unable to exec /bin/cli.sh: No such file or directory #36

Open tiagofreire-pt opened 3 years ago

tiagofreire-pt commented 3 years ago 
Debian GNU/Linux 10 hassio tty1

hassio login: root (automatic login)

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
ifelse: fatal: unable to exec /bin/cli.sh: No such file or directory
[cmd] /bin/cli.sh exited 127
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Debian GNU/Linux 10 hassio tty1

hassio login: root (automatic login)

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
ifelse: fatal: unable to exec /bin/cli.sh: No such file or directory
[cmd] /bin/cli.sh exited 127
[cont-finish.d] executin

On an older HA instance, I'm getting these cyclic errors. No CLI is available on the LXC. How can I fix this?

whiskerz007 commented 3 years ago

The best advice I have is to recreate the container, and import the snapshot. If the problem persists after creating a new container, I'll look further into it. HA devs sometimes make changes that requires the OS to be setup a little different.

tiagofreire-pt commented 2 years ago

Again, almost a year after this, the issue reappears.

Is there any way to access the data inside the LXC?