Posts by liquidJiggy

    Finally got it working. As with the reference above there is a fix for 3 different files which are permission based. Please reference the link above for the fix of each file, I've included the location of the files below. Once the files are updated then delete the container, not the volume or image, and restart the container as mentioned in the @TechnoDadLife video or the nextcloudpi website. Hopefully this will help others until the docker image is updated with the fix.

    File locations:

    It looks like this issue was identified and fixed in the github repository. I examined the latest docker image where these fixes should be inserted and it doesn't look like ownyourbits/nextcloudpi-armhf:latest has the fix included. This is running the command recommended in the video and on the nextcloudpi website.


    Try showing the permissions for the disk and directory.

    Also take a look at this. Docker ownyourbits/nextcloudpi-armhf with custom data directory

    Did you remove noexec?

    Ok, made it a little further thanks to the link you referenced. Through the link I also read another user experiencing a similar issue, see link below. I found the fstab file contained a reference to the new hard drive and also had noexec. Once I removed that I stopped nextcloudpi, removed it, deleted the volume, and then restarted OMV. I'm back to my original error but at least I resolved the previous one. Baby steps.

    docker logs -f nextcloudpi

    Making /usr/local/etc/ncp-config.d persistent ...
    Making /etc/services-enabled.d persistent ...
    Making /etc/letsencrypt persistent ...
    Making /etc/shadow persistent ...
    Making /etc/cron.d persistent ...
    Making /etc/cron.daily persistent ...
    Making /etc/cron.hourly persistent ...
    Making /etc/cron.weekly persistent ...
    Making /usr/local/bin persistent ...
    Making /etc/apache2 persistent ...
    Starting PHP-fpm
    Starting Apache
    Starting mariaDB
    2020-02-11 23:24:19 0 [Note] mysqld (mysqld 10.3.15-MariaDB-1) starting as process 141 ...
    Starting Redis
    277:C 11 Feb 2020 23:24:20.769 # Fatal error, can't open config file '/etc/redis/redis.conf'


    First, I think you need a disk attached to make this work.Second, delete everything and reinstall. You have an error that seems to be unique enough that nothing comes up when checking google.

    I was able to locate a spare 500GB hard drive. The good news is I'm no longer receiving the specific error mentioned earlier. The bad news is it's now a different error. In the logs I receive the error below. The permissions for the directory look good unless there is somewhere else I should be looking. I've removed the container and re-downloaded the image but so far it's still the same error.

    / line 47: /etc/services-enabled.d/010lamp: Permission denied
    / line 47: /etc/services-enabled.d/020nextcloud: Permission denied

    I greatly enjoy the videos @TechnoDadLife, they are easy to follow. I'm running into an installation issue however. My environment is a RockPro64 4GB, no hard drives, with a 64GB microSD card. This is only to test the installation with my intention to see if I can path to my Synology and use that for data storage. At any rate I'm receiving the following error in the logs:

    Starting Redis
    -1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">282:C 29 Jan 2020 23:18:45.490 # Fatal error, can't open config file '/etc/redis/redis.conf'

    I can log into the NextCloud activation screen but when I click Activate a spinning icon is displayed along with "NextCloudPi not yet initialized, trying again in a few seconds ...". I don't know if this is related to the Redis error. Thank you for any information or guidance with this issue.

    I really like what I see so far and I see no reason at this time to be considering a Synology or Qnap system

    OMV has been successfully loaded virtually. I really like what I see so far and I see no reason at this time to be considering a Synology or Qnap system. There is no sense in putting money into someone else's pocket to help their retailing markups when I can pick and choose the components that I wish.

    I have a Synology 412+ and from my limited experience with OMV I find it responds and has similar features to Synology's DSM. I'm already looking at getting a SoC, Rockpro64 or Raspberry Pi 3, for a replacement as it is significantly cheaper, at least for my current usage and set up.

    Thank you for the reply ryecoaaron and the recommendation. I am in the US so I will check out ameridroid for ordering. This really does look like a better investment than my initial investment with Synology a few years back.

    I've been thinking about converting my existing NAS setup, Synology 412+, into a SoC NAS. My current implementation is file storage with RAID 1 with an external backup, MariaDB, as well as several Docker images such as Openfire and GiTea. I'm looking to start using NextCloud, as well as their apps, which might eat into my existing Synology resources. After reviewing costs associated with a new motherboard, cpu, ram, physical size, and power consumption for an upgrade I think a SoC might be the better solution. The RockPro64 seems like this would certainly fit the bill and of course using OpenMediaVault. At any rate that is what I'm exploring and my current and future NAS usage.

    I think my only concern is the development team, Pine64, their website doesn't exactly explain who they are or where they operate from. I had to do some searching and found they are headquarted in San Fran, CA, according to Crunchbase. Does anyone have experience with ordering from Pine64 or their products?


    Well after a little more reading I found Ubuntu, which is Debian based, has an i386 docker repository. I installed through Shell in a Box and and after running the test installation everything appears to be functional. It still has Ubuntu branding but credit to Canonical for making the effort. Now I just need to figure out how to make it available through OMV. Any suggestions?

    Ubuntu i386

    Alternate link…

    Docker test installation…#test-docker-installation

    So after reading further it appears docker has decided to only build with 64-bit however 32-bit can be built from their static binaries. The following links are what I've been able to gather that are related to installing or building docker ce 32-bit.

    Build docker daemon…on-for-x32-architectures/

    Install docker ce i386

    Support for installing docker ce i386 on ubuntu…chine-having-ubuntu-12-04

    Build docker ce 32-bit from static binaries

    I'll leave this here for reference as I don't have time to dig deeper at the moment.

    Thank you for your suggestion and effort. I'll check the older docker package from the debian repos as you mentioned. As OMV extras Docker doesn't work with i386, would it be possible to include a x64-bit only tag in the description? I think that would help with others that may experience the same thing.

    I'm receiving a docker install error. It may be something simple I am missing. So far I have un-installed OMV extras, deleted the cache from the browser, and re-installed OMV extras. Thank you for any suggestions.

    Current setup:
    Dell Precision 650
    2 GB Ram
    80 GB IDE hard drive
    Xeon E7505 (3.06 GHz) CPU
    NVIDEA Quadro FX (DVI) video card
    OMV version 4.1.13-1 (Arrakis)

    OMV installation method: Debian iso and then OMV4 through https://openmediavault.readthe…stallation/on_debian.html.
    OMV extras installation: Download from and install.

    Thank you for the very fast response. I'm used to waiting 2 or more days on various other forms for anyone to actually reply. Believe me I would like to install OMV4 but as mentioned it's a 32-bit system. From what I understand OMV3 can be updated to the latest OMV4 so as soon as I can access the system that is what I intend to do.

    As an update I searched outside of OMV forums and found a solution. The problem was more basic at the linux level not with OMV that I know of. Modifying GRUB with nomodeset allowed me to view the monitor, so now I can at least manipulate the system. The link I used for the work around was which provided excellent step by step instructions.

    Anyway I thought to keep this thread updated if anyone else encounters a similar problem. Now I need to tackle the WebGUI access and enable SSH. Thank you again.