All the latest ONLYOFFICE Dockers are working except the Community Server one

[UNRA1DUser]

I created the following Docker with the Instructions from OnlyOffice.

 

onlyoffice-mysql-server: mysql:8.0.29
onlyoffice-community-server: onlyoffice/communityserver:12.0.1.1748
onlyoffice-elasticsearch: onlyoffice/elasticsearch:7.16.3
onlyoffice-document-server: onlyoffice/documentserver:7.1.1.23
onlyoffice-mail-server: onlyoffice/mailserver:1.6.75
onlyoffice-control-panel: onlyoffice/controlpanel:3.1.1.467

 

Every Server except the onlyoffice-community-server is working as expected. If I start the community Server I get those Docker logs.

 

sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
sed: -e expression #1, char 52: unknown option to `s'
+ find /var/www/onlyoffice/WebStudio -type f -name '*.json' -exec sed -i 's_\("core.machinekey":\|"machinekey":\).*,_\1 "core_secret",_' '{}' ';'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
+ for i in "${!binDirs[@]}"
+ find /etc/onlyoffice/communityserver -type f -name '*.[cC]onfig' -exec sed -i '/core.\machinekey/s_\(value\s*=\s*"\)[^"]*"_\1core_secret"_' '{}' ';'
sed: -e expression #1, char 52: unknown option to `s'
+ find /etc/onlyoffice/communityserver -type f -name '*.json' -exec sed -i 's_\("core.machinekey":\|"machinekey":\).*,_\1 "core_secret",_' '{}' ';'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
sed: -e expression #1, char 53: unknown option to `s'
+ continue
+ sed 's/{{APP_NIGNX_KEEPLIVE}}/32/g' -i /app/config/nginx/prepare-onlyoffice
+ bash -c 'echo "onlyoffice ALL=(ALL) NOPASSWD: /usr/sbin/service" | (EDITOR="tee -a" visudo)'
onlyoffice ALL=(ALL) NOPASSWD: /usr/sbin/service
+ '[' false == true ']'
+ systemctl enable redis-server.service
Synchronizing state of redis-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable redis-server
+ service redis-server start
/etc/init.d/redis-server: 51: ulimit: error setting limit (Operation not permitted)
Starting redis-server: redis-server.
+ redis-cli config set save ''
OK
+ redis-cli config rewrite
OK
+ redis-cli flushall
OK
+ service redis-server stop
Stopping redis-server: redis-server.
+ '[' SERVER == SERVICES ']'
+ systemctl enable monoserveApiSystem.service
++ seq 1 1
+ for serverID in $(seq 1 ${APP_MONOSERVE_COUNT})
+ index=1
+ '[' 1 == 1 ']'
+ index=
+ systemctl enable monoserve.service
+ chown -R onlyoffice:onlyoffice /var/log/onlyoffice
+ chown -R onlyoffice:onlyoffice /var/www/onlyoffice/DocumentServerData
++ ls -alhd /var/www/onlyoffice/Data
++ awk '{ print $3 }'
+ '[' onlyoffice '!=' onlyoffice ']'
+ '[' '!' -d /var/www/onlyoffice/Data/Index/v7.16.3 ']'
+ mkdir -p /var/log/onlyoffice//Index
+ mkdir -p /var/www/onlyoffice/Data/Index/v7.16.3
++ ls -alhd /var/www/onlyoffice/Data/Index/v7.16.3
++ awk '{ print $3 }'
+ '[' elasticsearch '!=' elasticsearch ']'
+ chown -R elasticsearch:elasticsearch /var/log/onlyoffice//Index
+ dpkg -l
+ grep -q onlyoffice-xmppserver
+ sed '/web\.talk/s/value=\"\S*\"/value=\"true\"/g' -i /var/www/onlyoffice/WebStudio/web.appsettings.config
+ sed '/web\.chat/s/value=\"\S*\"/value=\"false\"/g' -i /var/www/onlyoffice/WebStudio/web.appsettings.config
+ systemctl stop onlyofficeRadicale
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeTelegram
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeSocketIO
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeThumb
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeFeed
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeIndex
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeJabber
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeMailAggregator
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeMailWatchdog
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeMailCleaner
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeMailImap
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeNotify
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeBackup
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeStorageMigrate
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeStorageEncryption
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeUrlShortener
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeThumbnailBuilder
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop onlyofficeAutoCleanUp
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop god
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl enable god
+ systemctl stop elasticsearch
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop redis-server
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop mysql
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop nginx
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl stop monoserveApiSystem.service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl enable monoserveApiSystem.service
++ seq 1 1
+ for serverID in $(seq 1 ${APP_MONOSERVE_COUNT})
+ index=1
+ '[' 1 == 1 ']'
+ index=
+ systemctl stop monoserve.service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl enable monoserve.service
+ '[' false == true ']'
+ systemctl enable onlyofficeRadicale.service
+ systemctl enable onlyofficeTelegram.service
+ systemctl enable onlyofficeSocketIO.service
+ systemctl enable onlyofficeThumb.service
+ systemctl enable onlyofficeFeed.service
+ systemctl enable onlyofficeIndex.service
+ systemctl enable onlyofficeJabber.service
+ systemctl enable onlyofficeMailAggregator.service
+ systemctl enable onlyofficeMailWatchdog.service
+ systemctl enable onlyofficeMailCleaner.service
+ systemctl enable onlyofficeMailImap.service
+ systemctl enable onlyofficeNotify.service
+ systemctl enable onlyofficeBackup.service
+ systemctl enable onlyofficeStorageMigrate.service
+ systemctl enable onlyofficeStorageEncryption.service
+ systemctl enable onlyofficeUrlShortener.service
+ systemctl enable onlyofficeThumbnailBuilder.service
+ systemctl enable onlyofficeAutoCleanUp.service
Failed to enable unit, unit onlyofficeAutoCleanUp.service does not exist.
+ '[' SERVER == SERVER ']'
+ mv /app/config/nginx/prepare-onlyoffice /etc/nginx/sites-enabled/onlyoffice
+ service nginx stop
 * Stopping nginx nginx
   ...done.
+ systemctl enable nginx.service
Synchronizing state of nginx.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable nginx
++ ps auxf
++ grep cron
++ grep -v grep
++ awk '{print $2}'
+ PID=
+ '[' ONLYOFFICE-Elasticsearch-Official ']'
+ service elasticsearch stop
elasticsearch: unrecognized service
+ systemctl disable elasticsearch.service
Failed to disable unit, unit elasticsearch.service does not exist.
+ rm -f /usr/lib/systemd/system/elasticsearch.service
+ rm -f /etc/init.d/elasticsearch
+ '[' -n '' ']'
+ rm -dfr '/tmp/onlyoffice*'
+ rm -dfr '/var/run/onlyoffice/*'
+ rm -dfr '/var/cache/nginx/onlyoffice/*'
+ '[' true == true ']'
+ exec /lib/systemd/systemd

 

Systemd is not working in Unraid Dockers. So I think that Docker is using systemctl instead. That should be fine.

I also red on the ONLYOFFICE Page that the latest Version of Docker is needed to install it. Unraid is some versions behind the latest one. Is there a way to Update the Docker Version? Could that be the Problem? Or do you have any other Idea about it?

 

Thanks!

 

[primeval_god]

On 1/19/2024 at 1:39 PM, UNRA1DUser said:

Systemd is not working in Unraid Dockers. So I think that Docker is using systemctl instead. That should be fine.

systemctl is part of Systemd they are not different things.

 

On 1/19/2024 at 1:39 PM, UNRA1DUser said:

I also red on the ONLYOFFICE Page that the latest Version of Docker is needed to install it. Unraid is some versions behind the latest one. Is there a way to Update the Docker Version? Could that be the Problem? Or do you have any other Idea about it?

There is no simple way to update components like the docker engine separate from an OS release in unRAID. Regardless it is unlikely to be an issue with the version of the Docker Engine. It is more likely to be an error in how your configuring the container. Unfortunately i know nothing about onlyoffice so i cant really help there.

[UNRA1DUser]

Thanks!

 

In the OnlkyOffice Forum is no one helping. They are just telling me, that I should use a newer Docker Version and than it should work.