# CODE is running an old version despite docker container is stopped **URL:** \ **Category:** Installation & Configuration\ **Created:** [October 18, 2024, 2:20pm UTC](https://forum.collaboraonline.com/t/code-is-running-an-old-version-despite-docker-container-is-stopped/3086 "2024-10-18T14:20:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Angel](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@Angel](https://forum.collaboraonline.com/u/Angel)\ **Post date:** [October 18, 2024, 2:20pm UTC](https://forum.collaboraonline.com/t/code-is-running-an-old-version-despite-docker-container-is-stopped/3086/1 "2024-10-18T14:20:58Z")
Hello, I have a strange situation. I recently updated NextCloud to Nextcloud Hub 9 (30.0.1) and I also pulled the last collabora CODE from dockerhub. Before the installation everything was working fine. The container is stuck restarting and the logs show the following ```auto wsd-00001-00001 2024-10-18 14:20:25.932190 +0000 [coolwsd] WRN File not found: Private key file: /etc/coolwsd/proof_key No proof-key will be present in discovery. If you need to use WOPI security, generate an RSA key using this command: sudo coolconfig generate-proof-key or if your config dir is not /etc, you can run ssh-keygen manually: ssh-keygen -t rsa -N "" -m PEM -f "/etc/coolwsd/proof_key" Note: the proof_key file must be readable by the coolwsd process.| wsd/ProofKey.cpp:151 wsd-00001-00001 2024-10-18 14:20:25.933337 +0000 [coolwsd] TRC #14: Created socket. Thread affinity set to 0x7fa973cbc880| net/Socket.hpp:384 wsd-00001-00001 2024-10-18 14:20:25.933349 +0000 [coolwsd] ERR #14: Failed to bind to: IPv6 port: 9980 (EADDRINUSE: Address already in use)| net/Socket.cpp:1048 Failed to listen on Server port(s) (9980-9980). Exiting wsd-00001-00001 2024-10-18 14:20:25.933370 +0000 [coolwsd] TRC #14: Socket dtor| net/Socket.hpp:150 wsd-00001-00001 2024-10-18 14:20:25.933379 +0000 [coolwsd] DBG #14: Closed socket to []| net/Socket.hpp:155 wsd-00001-00001 2024-10-18 14:20:25.933401 +0000 [coolwsd] FTL Failed to listen on Server port(s) (9980-9980). Exiting| wsd/COOLWSD.cpp:4253 Forced Exit with code: 70 wsd-00001-00001 2024-10-18 14:20:25.933423 +0000 [coolwsd] FTL Forced Exit with code: 70| common/Util.cpp:819 ``` After stopping and even removing the docker container, I can still edit documents using CODE, however it is running an older version ```auto COOLWSD version: 23.05.8.4 git hash: 96e80a8 (E) LOKit version: built on a great technology base Collabora Office 23.05.8.4 git hash: c5262f7 Served by: Debian GNU/Linux 12 (bookworm) b350cfe7 Copyright © 2024, Collabora Productivity Limited. ``` I’ve also checked what executable is using the port 9980 and I get this: ```auto COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME coolwsd 4132447 systemd-network 15u IPv6 1552036625 0t0 TCP *:9980 (LISTEN) coolwsd 4132447 systemd-network 18u IPv6 1554435485 0t0 TCP localhost.localdomain:9980->localhost.localdomain:33886 (ESTABLISHED) nginx 4162783 nginx 83u IPv4 1554434798 0t0 TCP localhost.localdomain:33886->localhost.localdomain:9980 (ESTABLISHED) ``` and the executable location points to `/usr/bin/coolwsd` (executing `readlink -f /proc/4132447/exe`) Is Nextcloud somehow running an old CODE version? Visiting the UI on `nextcloud/index.php/settings/admin/richdocuments` shows the following (I configured it to use my own server): ```auto Collabora Online server is reachable. Collabora Online Development Edition 23.05.8.4 96e80a8 ``` and the URLs shown are also the correct ones. Does anyone have a clue what could be possibly happening? Thank you ---
**Author:** ![Angel](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@Angel](https://forum.collaboraonline.com/u/Angel)\ **Post date:** [October 19, 2024, 6:56pm UTC](https://forum.collaboraonline.com/t/code-is-running-an-old-version-despite-docker-container-is-stopped/3086/2 "2024-10-19T18:56:33Z")
Update: After killing the process it respawns again, but the command `systemctl status coolwsd` yields `Unit coolwsd.service could not be found.` and I have made sure the docker daemon is not running. What else could be executing collabora code? ---
**Author:** ![Angel](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@Angel](https://forum.collaboraonline.com/u/Angel)\ **Post date:** [October 19, 2024, 7:17pm UTC](https://forum.collaboraonline.com/t/code-is-running-an-old-version-despite-docker-container-is-stopped/3086/3 "2024-10-19T19:17:10Z")
I managed to get the latest version running. What I did was ‘sudo snap disable docker’ and then ‘sudo snap enable docker’ and somehow that allowed me to install the latest image and run it without an issue. ---
**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\ **Post date:** [October 21, 2024, 6:28am UTC](https://forum.collaboraonline.com/t/code-is-running-an-old-version-despite-docker-container-is-stopped/3086/4 "2024-10-21T06:28:59Z")
Awesome @Angel it seems you have solved the problem all by yourself. Kudos 🎉 ---
**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\ **Post date:** [October 22, 2024, 12:01pm UTC](https://forum.collaboraonline.com/t/code-is-running-an-old-version-despite-docker-container-is-stopped/3086/5 "2024-10-22T12:01:38Z")