Posts by Nefertiti

    So far so good but I got stuck with ports I want to change the ports this way

    docker run -d -p 4443:4443 -p 460:443 -p 85:80 -v /srv/dev-disk-by-label-WD_10TB_1/AppData/ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf

    but I cannot access the nexcloud pages, and I think it has to do with apache2 but not sure how to modify those?



    <VirtualHost _default_:80>
    DocumentRoot /var/www/nextcloud
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{HTTPS} !=on
    RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]

    I deleted the container rename ncdata old recreated everything with but got an error

    WARNING: Error loading config file: /root/.docker/config.json: read /root/.docker/config.json: is a directory

    docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v /srv/dev-disk-by-label-WD_10TB_1/AppData/ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf
    WARNING: Error loading config file: /root/.docker/config.json: read /root/.docker/config.json: is a directory

    Anyway is running but sill

    I cannot reach https://nextcloudpi.local or https://nextcloudpi.local:4443

    Like I said I do not have any issue to land on nextcloudPi Activation page using either


    but I cannot reach https://nextcloudpi.local or https://nextcloudpi.local:4443

    the latest error message is

    -1 }">2020-05-30 4:41:39 0 [Note] mysqld (mysqld 10.3.22-MariaDB-0+deb10u1) starting as process 226 ...
    -1 }">
    Starting Cron
    -1 }">
    Starting Postfix
    -1 }">
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)

    I decide to install nextcloudpi I ran into a first error saying 443 was used so I changed on the general page of OMV 443 by 453

    the second error is maybe because my docker storage is /srv/dev-disk-by-label-WD_10TB_1/docker

    docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v /srv/dev-disk-by-label-WD_10TB_1/AppData/ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf
    WARNING: Error loading config file: /root/.docker/config.json: read /root/.docker/config.json: is a directory

    so anyway I can get to the page NexcloudPi Activation no problem there, but I am unable to go to https://nextcloudpi.local:4443/ or so I cannot continue the config!

    in the log I am also getting The current PHP memory limit is below the recommended value of 512MB.

    So How to correct those errors?

    Actually I am getting some errors I think the network is not reachable how to fix that?

    Also according the instructions from I should be able to pass an expreesion to clean up in the docker run string: How can I enter s this option in portainer?

    docker run --rm v2tec/watchtower --cleanup

    I was formatting an external ssd ext4 try to mount it the whole system crashed took 4 mn to boot and was landing first on

    Error #0: OMV\HttpErrorException: Invalid IP address. in /usr/share/php/openmediavault/ Stack trace: #0 /usr/share/php/openmediavault/ OMV\Session->validateIpAddress() #1 /var/www/openmediavault/index.php(34): OMV\Session->validate() #2 {main}

    and now getting

    I did not have time to backup that one Grrr!

    Can it be fixed?

    In any case trying

    apt-get install --reinstall openmediavault

    well stiil crashing with putty

    I removed the exta argument under label i put the Bind mount /etc/localtime:/etc/localtime not sure if watch tower is working the log just says time="2020-05-23T14:49:27-07:00" level=info msg="First run: 2020-05-23 14:54:27 -0700 PDT"

    I have a cron job docker images -q --filter "dangling=true" | xargs -n1 -r docker rmi

    but right now it does not do anything , am I missing something?

    Should I put this in all my container I had /etc/localtime in volumes mount in all my container I deleted them since I did not understand the use of them, should I put them back as mount /etc/localtime:/etc/localtime ?

    An earlier version of OMV, when upgraded in place to OMV 5 will not remove or depopulate any files or folders in /sharedfolders that were created there by the previous version of OMV. They should continue to work or cause problems just like they did in the prior version installation because it is the container configurations that still have these settings until you change them.

    I do not know however, whether or not such an upgraded installation will create new folders in /sharedfolders when new shares are created (following the prior version behavior), or no longer create them (as is the default behavior in a fresh install of OMV 5). I do know that this behavior is user configurable via an environment variable setting in /etc/default/openmediavault

    Regardless, there were reasons for deprecating this behavior in OMV 5. I do not have a list of these reasons and how they rank with respect to causing problems. But using /sharedfolders paths in docker volume and bind mounts is a reason, and may be a major reason.

    Anyway i saw this post from@ryecoaaron RE: Sharedfolder but I wont change it since It does not look I need the path with sharefolders and it is working the way it is, now?

    So it is What I thought but one of my upgraded omv 5 was working with relative path I think the upgrade did not perform completely and in a way was giving me errors inot related to this matter like netfilter failure.

    Not sure but I think this upgrade did not complete fully this is why with this SD, it is working this way on an other upgrade the relative paths are not working?

    Sounds like docker starting before you storage is ready. I added to the plugin to start docker after the local filesystems are done but some usb drives/remote mounts/mergerfs pool on top of filesystem on top luks have issues being mounted before docker starts. Restarting docker would probably fix it or adding the gross override to just wait 30secs for storage to be ready.

    I do not know if is related: I got 2 sd both with OMV5 and without changing anything in dockers ( relative paths) one of them make me land on a generic welcome page for Emby, Jellyfish, Airsonic and probably some other But I have not check them, the other OMV5 give me regular working library for those and I think I applied this mod for both Is your docker also corrupt after a reboot? (OMV5, Pi4) This might fix it!

    I must say I would agree with gwaitsi although I do not use plugin, but docker at this time is definitely not working as smooth as omv4. I keep struggling for over a week with version 5, and I see myself going back and forth between both systems.

    One among some issues, having this problem where portainer disappearing and cannot be reinstalled, also volumes path not always working

    I did not give up on OMV5 but hopefully with some subsequent update all those issues will be past history, but for now I think OMV 5 is not really ready yet for prime time .