That's exactly the same thing on my setup. But I think u meant apt-get upgrade instead of update.
Errors installing docker on OMV4
-
-
-
Do not know how exactly but i think i fixed
-
i used this link : https://askubuntu.com/question…locked-by-another-process
for fixing dpkg --configure -a
and then just fallowed rest of the steps, restarted pi and was working fine
-
I really can't figure out what was going wrong on any of your systems. All I did was flash the image and boot it. After about half an hour (VERY IMPORTANT since the image is making changes), I made sure the system was fully up to date. I checked to see if the ip_tables module was loaded and it was. Then for debugging purposes, I installed docker-ce from the command and it worked. Installing from the command line doesn't do anything any different from the web interface. So, this didn't magically prevent the problem.
I haven't watched the video but you normally shouldn't have to do a dpkg --configure. If something says the dpkg database is busy, it is. Don't do anything because OMV has a process that downloads updates. Just wait for it to be not busy. If someone is interrupting this, this might explain how your system got in a bad state.
The omv-initsystem popup showing up or not showing up makes no difference. Don't consider that a sign of failure or success.
-
in any case i am happy that finally i moved forward with this project, tomorrow ill have hdds's and new adventure will begin
-
I really can't figure out what was going wrong on any of your systems. All I did was flash the image and boot it. After about half an hour (VERY IMPORTANT since the image is making changes), I made sure the system was fully up to date. I checked to see if the ip_tables module was loaded and it was. Then for debugging purposes, I installed docker-ce from the command and it worked. Installing from the command line doesn't do anything any different from the web interface. So, this didn't magically prevent the problem.
I haven't watched the video but you normally shouldn't have to do a dpkg --configure. If something says the dpkg database is busy, it is. Don't do anything because OMV has a process that downloads updates. Just wait for it to be not busy. If someone is interrupting this, this might explain how your system got in a bad state.
The omv-initsystem popup showing up or not showing up makes no difference. Don't consider that a sign of failure or success.
I just did a clean install and run in the same problem. I let the Pi sit for 40 min and everything went smooth until I wanted to install shellinabox and docker.
heres the log from the installation screen:
install log.txt
when I put in
nothing happens..now what?
edit:
I needed to use omv-firstaif to enable the web interface, if that is of any help.I tried to find a solution to fix the iptables problem and ended up with:
Coderoot@RaspberryPiNAS:~# ls -la /lib/modules/4.9.80-v7+ ls: cannot access '/lib/modules/4.9.80-v7+': No such file or directory
In the other thread from 2016 they said that this was bad and one should reinstall. but as I just did that I dont see any sense in that.
-
I needed to use omv-firstaif to enable the web interface, if that is of any help.
That means something went very wrong.
I tried to find a solution to fix the iptables problem and ended up with:
The image is using the 4.14 kernel now. So, that directory will not exist. find /lib/modules/ -name "ip_tables*" will show you if the module exists. Here is mine:
/lib/modules/4.14.70-v7+/kernel/net/ipv4/netfilter/ip_tables.ko
/lib/modules/4.14.70+/kernel/net/ipv4/netfilter/ip_tables.ko
/lib/modules/4.14.47-rockchip/kernel/net/ipv4/netfilter/ip_tables.ko -
Whilst this doesn't help you but I just upgraded from v3 to v4, once complete I did an update, set time, monitoring etc, then did wget -O - http://omv-extras.org/install | bash from the command line to install omv-extras when that was complete enabled the Docker-CE Repo within extras, then installed the docker-gui plugin.
Docker has installed with just the usual php error which is nothing to worry about.
I have Pi 2B
-
I just did another clean install and had to use omv-firstaid to enable the webinterface. I could ony acces the Pi with an attached screen and keyboard
I then did
after that I went to the webinterface to enable docker ce within the omv-extras. and then this:Code
Alles anzeigenroot@raspberrypi:~# lsmod | grep ip ip_tables 24576 0 x_tables 32768 1 ip_tables ipv6 434176 97 root@raspberrypi:~# apt-get install docker-ce Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: aufs-tools cgroupfs-mount | cgroup-lite pigz The following NEW packages will be installed: docker-ce 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 28.3 MB of archives. After this operation, 137 MB of additional disk space will be used. Get:1 https://download.docker.com/linux/debian stretch/stable armhf docker-ce armhf 18.06.1~ce~3-0~debian [28.3 MB] Fetched 28.3 MB in 22s (1,265 kB/s) Selecting previously unselected package docker-ce. (Reading database ... 51361 files and directories currently installed.) Preparing to unpack .../docker-ce_18.06.1~ce~3-0~debian_armhf.deb ... Unpacking docker-ce (18.06.1~ce~3-0~debian) ... Setting up docker-ce (18.06.1~ce~3-0~debian) ... Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service. Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket. Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2018-09-27 19:14:24 UTC; 29ms ago Docs: https://docs.docker.com Process: 17480 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 17480 (code=exited, status=1/FAILURE) CPU: 731ms Sep 27 19:14:24 raspberrypi systemd[1]: docker.service: Unit entered failed …te. Sep 27 19:14:24 raspberrypi systemd[1]: docker.service: Failed with result '…e'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package docker-ce (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (232-25+deb9u4) ... Processing triggers for man-db (2.7.6.1-2) ... Errors were encountered while processing: docker-ce Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x76309390> Traceback (most recent call last): File "/usr/lib/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x76309390> Traceback (most recent call last): File "/usr/lib/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Contents-deb (main/Contents-armhf) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Contents-deb (main/Contents-all) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Packages (contrib/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Contents-deb (contrib/Contents-armhf) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Contents-deb (contrib/Contents-all) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Packages (non-free/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Contents-deb (non-free/Contents-armhf) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 W: Target Contents-deb (non-free/Contents-all) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1 E: Sub-process /usr/bin/dpkg returned an error code (1) root@raspberrypi:~# lsmod | grep ip ip_tables 24576 0 x_tables 32768 1 ip_tables ipv6 434176 94
I still get the docker error but atleast the ip tables still work.
where did you download your image? I got mine from https://sourceforge.net/projec…2_3_3Plus.img.xz/download
I know this shouldnt matter, but I cant see what Im doing wrongedit:
I forgot to mention that I installed shellinabox from witin the webinterface. -
I just did another clean install and had to use omv-firstaid to enable the webinterface.
You shouldn't have to do that. Are you using etcher?
I still get the docker error but atleast the ip tables still work.
What is the output of: journalctl -u docker
where did you download your image?
Sourceforge (I also uploaded it there).
I forgot to mention that I installed shellinabox from witin the webinterface.
I don't think that should be a problem but I have installed the plugin lately.
-
W: Target Contents-deb (non-free/Contents-armhf) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1
W: Target Contents-deb (non-free/Contents-all) is configured multiple times in /etc/apt/sources.list:7 and /etc/apt/sources.list.d/openmediavault-kernel-backports.list:1Apart from the fact that those need sorting what's the output of dpkg --configure -a
-
Are you using etcher?
yes
What is the output of: journalctl -u docker
Code
Alles anzeigenroot@raspberrypi:~# journalctl -u docker -- Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Fri 2018-09-28 14:14:32 Sep 27 19:14:23 raspberrypi systemd[1]: Starting Docker Application Container Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23.4117225 Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23.4138122 Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23.4156441 Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23.4177580 Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23.4179491 Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23.4183323 Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level Sep 27 19:14:23 raspberrypi dockerd[17480]: time="2018-09-27T19:14:23Z" level lines 1-43
Apart from the fact that those need sorting what's the output of dpkg --configure -a
Code
Alles anzeigenroot@raspberrypi:~# dpkg --configure -a Setting up docker-ce (18.06.1~ce~3-0~debian) ... Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2018-09-28 14:15:36 UTC; 30ms ago Docs: https://docs.docker.com Process: 19130 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 19130 (code=exited, status=1/FAILURE) CPU: 599ms Sep 28 14:15:36 raspberrypi systemd[1]: docker.service: Unit entered fail…te. Sep 28 14:15:36 raspberrypi systemd[1]: docker.service: Failed with resul…e'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package docker-ce (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker-ce
Code
Alles anzeigenroot@raspberrypi:~# systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e Active: failed (Result: exit-code) since Fri 2018-09-28 16:15:38 CEST; 21min Docs: https://docs.docker.com Main PID: 19338 (code=exited, status=1/FAILURE) CPU: 676ms Sep 28 16:15:38 raspberrypi systemd[1]: docker.service: Unit entered failed stat Sep 28 16:15:38 raspberrypi systemd[1]: docker.service: Failed with result 'exit Sep 28 16:15:38 raspberrypi systemd[1]: docker.service: Service hold-off time ov Sep 28 16:15:38 raspberrypi systemd[1]: Stopped Docker Application Container Eng Sep 28 16:15:38 raspberrypi systemd[1]: docker.service: Start request repeated t Sep 28 16:15:38 raspberrypi systemd[1]: Failed to start Docker Application Conta Sep 28 16:15:38 raspberrypi systemd[1]: docker.service: Unit entered failed stat Sep 28 16:15:38 raspberrypi systemd[1]: docker.service: Failed with result 'exit root@raspberrypi:~# journalctl -xe Sep 28 16:37:04 raspberrypi sshd[20211]: Accepted password for root from 192.168 Sep 28 16:37:04 raspberrypi sshd[20211]: pam_unix(sshd:session): session opened Sep 28 16:37:04 raspberrypi systemd[1]: Started Session c5 of user root. -- Subject: Unit session-c5.scope has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit session-c5.scope has finished starting up. -- -- The start-up result is done. Sep 28 16:37:04 raspberrypi systemd-logind[695]: New session c5 of user root. -- Subject: A new session c5 has been created for user root -- Defined-By: systemd -- Support: https://www.debian.org/support -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID c5 has been created for the user root. -- -- The leading process of the session is 20211. Sep 28 16:37:38 raspberrypi wpa_supplicant[913]: wlan0: Failed to initiate sched Sep 28 16:38:01 raspberrypi CRON[20344]: pam_unix(cron:session): session opened Sep 28 16:38:01 raspberrypi CRON[20348]: (root) CMD (for i in `pgrep "ftpd|nfsio Sep 28 16:38:01 raspberrypi CRON[20344]: pam_unix(cron:session): session closed lines 1264-1286/1286 (END)
-
This is seriously shot to bits and it should just work!
Ok try what @ryecoaaron told @timbataoapt-get purge openmediavault-docker-gui
apt-get purge openmediavault-omvextrasorg
dpkg -l | grep openm -
This is seriously shot to bits and it should just work!
Ok try what @ryecoaaron told @timbataoapt-get purge openmediavault-docker-gui
apt-get purge openmediavault-omvextrasorg
dpkg -l | grep openmCode
Alles anzeigenroot@raspberrypi:~# apt-get purge openmediavault-docker-gui Reading package lists... Done Building dependency tree Reading state information... Done Package 'openmediavault-docker-gui' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up docker-ce (18.06.1~ce~3-0~debian) ... Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2018-09-28 18:13:26 CEST; 34ms ago Docs: https://docs.docker.com Process: 23646 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 23646 (code=exited, status=1/FAILURE) CPU: 638ms CGroup: /system.slice/docker.service Sep 28 18:13:26 raspberrypi systemd[1]: Failed to start Docker Application C…ne. Sep 28 18:13:26 raspberrypi systemd[1]: docker.service: Unit entered failed …te. Sep 28 18:13:26 raspberrypi systemd[1]: docker.service: Failed with result '…e'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package docker-ce (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker-ce Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x76330390> Traceback (most recent call last): File "/usr/lib/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x76330390> Traceback (most recent call last): File "/usr/lib/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable E: Sub-process /usr/bin/dpkg returned an error code (1) root@raspberrypi:~# apt-get purge openmediavault-omvextrasorg Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: openmediavault-omvextrasorg* 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 460 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 51650 files and directories currently installed.) Removing openmediavault-omvextrasorg (4.1.11) ... Setting up docker-ce (18.06.1~ce~3-0~debian) ... Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2018-09-28 18:14:11 CEST; 29ms ago Docs: https://docs.docker.com Process: 24065 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 24065 (code=exited, status=1/FAILURE) CPU: 665ms Sep 28 18:14:11 raspberrypi systemd[1]: docker.service: Unit entered failed …te. Sep 28 18:14:11 raspberrypi systemd[1]: docker.service: Failed with result '…e'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package docker-ce (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for openmediavault (4.1.11) ... Restarting engine daemon ... Errors were encountered while processing: docker-ce E: Sub-process /usr/bin/dpkg returned an error code (1) root@raspberrypi:~# dpkg -l | grep openm ii openmediavault 4.1.11 all openmediavault - The open network attached storage solution ii openmediavault-flashmemory 4.1 all folder2ram plugin for OpenMediaVault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-netatalk 4.0.7-1 all OpenMediaVault netatalk (AppleTalk Protocol Suite) plugin ic openmediavault-omvextrasorg 4.1.11 all OMV-Extras.org Package Repositories for OpenMediaVault ii openmediavault-shellinabox 3.4 all Web-based SSH client. root@raspberrypi:~#
-
If the docker service won't stop, uninstalling the plugin fails. You have to remove the postrm file I mention on a previous page. I need to fix that in the plugin.
-
@Wilpe see @ryecoaaron and what I have posted after this post, do that first before this
dpkg -l | grep openm
That output is showing no docker.ce reference, are there any updates in Update Management to be installed? if there is install them.
Again starting from further up the thread;
wget -O - http://omv-extras.org/install | bash wait for this to complete...back to the GUI and omv-extras should appear on the left....go in and enable Docker-CE Repo you should have to apply/save confirm changes. The OMV-Extras.org should be enabled by default, if not enable it.
If that works go to plugins and install the docker-gui probably at the bottom of the list. -
If the docker service won't stop, uninstalling the plugin fails. You have to remove the postrm file I mention on a previous page. I need to fix that in the plugin.
So you're saying to do rm /var/lib/dpkg/info/openmediavault-docker-gui.postrm as well.
-
So you're saying to do rm /var/lib/dpkg/info/openmediavault-docker-gui.postrm as well.
Yes
-
As I was getting a bit frustrated I went ahead and bought a new 16GB class 10 sd card and flashed it. This time I didnt need to run omv-firstaid and could connect via putty straight away. I then did apt-get update, apt-get upgrade and went to the webinterface to install docker. For that I enabled docker within the extras and went to plugins when I started the install it told me that:
which I did and since then it is stuck at this screen I cant hit <ok>Code
Alles anzeigenroot@raspberrypi:~# dpkg --configure -a Setting up openmediavault (4.1.11) ... Updating configuration database ... Updating configuration ... monit.service is not a native service, redirecting to systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install is-enabled monit Package configuration ┌──────────────────────┤ Configuring openmediavault ├───────────────────────┐ │ │ │ Complete the installation │ │ To complete the installation you need to run the following command: │ │ omv-initsystem │ │ │ To manage the system visit the openmediavault web control panel via a │ web browser: │ │ http://<IP or hostname> │ │ │ By default the web control panel administrator account has the username │ │ <Ok>
should I stick with this installation or the last one? I think this one looks more promising.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!