[BUG] Fresh Install unable to launch

[koolsb]

Is there an existing issue for this?

• [X] I have searched the existing issues

Seems similar to #130 except I'm not running this via LXC, it is a native docker installation.

Current Behavior

Fresh install of Calibre will not start due to kasmvnc issue.

Expected Behavior

No response

Steps To Reproduce

1. Run docker run command or attempt to start via docker composer
2. container hangs

Environment

- OS: Debian 11 / bullseye
- How docker service was installed: packagemanager via docker supplied repositories
- Docker version: 23.0.5

CPU architecture

x86-64

Docker creation

docker run -d \
  --name=calibre \
  --security-opt seccomp=unconfined `#optional` \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=America/Chicago \
  -p 8080:8080 \
  -p 8181:8181 \
  -p 8081:8081 \
  lscr.io/linuxserver/calibre:latest

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

.........+.....+................+.....+...+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*.+......+.+.........+...........+...+.+...+......+..+....+.....+.+..+.+.....................+...+...+.....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*...+...........+....+..............+.+...+......+.....+......+.+.................................+.........+..+.+..+...+.......+......+............+...+.....+....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.........+......+.....+.+............+...+..+...+...+....+..+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*..+.....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*....+....+...+..+.......+...+........+...+.......+..+...+....+....................+....+......+...........+...............+...+...................+..+...+.......+......+...+..+...+.+.....+...+.+.....+.......+..+.+.........+.....+......+.+.....+.+..............+.............+.....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----
mv: cannot move '/usr/local/etc/kasmvnc/kasmvnc.yaml.lsio' to a subdirectory of itself, '/usr/local/etc/kasmvnc/kasmvnc.yaml'
s6-rc: warning: unable to start service init-kasmvnc-config: command exited 1

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Talung]

This is a simple fix.. took me a while to find it, but instead of using the mv function, use a cp and a rm one.

ie. cp /usr/local/etc/kasmvnc/kasmvnc.yaml.lsio /usr/local/etc/kasmvnc/kasmvnc.yaml rm /usr/local/etc/kasmvnc/kasmvnc.yaml.lsio

I do this within the docker container itself. It needs to be fixed on the build side.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[Talung]

This issue Still exists and have to run a script to manually do the cp everytime the docker is updated.

[aptalca]

See here for the underlying issue: https://forums.docker.com/t/unable-to-run-mv-when-building-any-image-all-mv-is-subdirectory-of-itself/137409

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[drizuid]

this is not reproducible in a setup supported by docker and there has been no input from the OP, closing this.

[github-actions[bot]]

This issue is locked due to inactivity