Posts by seanmccabe

  • Clean Install of latest OMV7 hangs during install

    Hi all,


    Attempting to install OMV7 clean and I keep running into hangs and problems during the network phase.


    Attempt using WiFi, constantly get it can't exchange keys.

    If I do enter SSID manually, then no issue and can progress to IPv6 DHCP and it gets to 100% then bluescreen with white strip and nothing.


    If using ethernet, goes all the way to configuring IPv6 DHCP and then the install hangs, same as above.


    I've left the screen for half hour and no progress at all, nothing on the USB led to indicate any activity.


    Only option is to ctrl+alt+delete.


    I'm going to try with ethernet unplugged, or skipping, see what happens.

    But there appears to be an issue of some description.

  • OMV5 to OMV6 Upgrade - How reliable/Stable?

    Quote from macom

    If you follow this process, it should work.

    And if you follow this process you make a backup of your OS drive (actually, you should always have one), so it is easy to go back if something goes wrong.


    Post
    RE: Is there a guide to in place upgrade?
    Contributions wanted:
    1. Backup the OS drive (this is allways a good idea, not only for upgrades)
    2. Make sure, you have enough free space on your os drive
    3. Check any installed plugins if they have been ported to OMV6
      If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
      (Many plugins can be replaced by docker containers. Do this before upgrading)
    4. If you installed
    …
    Zoki

    I do have the backup running, and that seem to be running every week, though not entirely sure of the process to actually restore it.

  • OMV5 to OMV6 Upgrade - How reliable/Stable?

    I've been thinking of doing the OMV6 upgrade for a while, but worried about how well it will go.


    Last time I upgraded from OMV4 to OMV5 it completely borked the upgrade and I ended up having to rebuild everything from scratch, it was painful.


    So my question is, in light of everyone's experience, should I upgrade?

    Are there any pitfalls, and things to be warry of when upgrading?


    If upgrading, what happens to Docker and my containers? Does everything need resetup on that side of things?


    Thanks

  • Docker doesn´t start after last upgrade to 5:23.0.0-1~debian.11~bullseye

    Quote from Sn00zE

    From RE: docker not working since omv-upgrade in OMV run the docker uninstall, SSH to your machine


    Code
    sudo apt install docker-ce-cli=5:20.10.23~3-0~debian-bullseye
sudo apt install docker-ce=5:20.10.23~3-0~debian-bullseye
sudo service docker restart

    This worked for me. I see the upgrade is available again. not sure if it will break it again without the fix from docker not working since omv-upgrade


    Its too hot here and too late to do this now, just needed things running again.

    haha, I was doing mine, whilst you were doing yours :)


    I maybe that I am on OMV5, so the fix doesn't actually work for me.


    I've not gone to OMV6, as last time I went from 4-5 it completely bricked the system, what was supposed to be an hour exercise turned into a day getting OMV5 installed fresh and setting everything back up.


    Not sure how stable to upgrade from 5-6 is now.

  • Docker doesn´t start after last upgrade to 5:23.0.0-1~debian.11~bullseye

    Ok, I went with going for an older version, and not going to v23.


    Do the following:


    Code
    apt-cache madison docker-ce
sudo apt-get install -y docker-ce={ insert the docker version from the list }


    I did version 20 and everything installed fine, Portainer came back, 0 issues.

    I will just stay at this I think, can't risk any further issues and clearly my system isn't compatible with whatever Docker 23 is trying to do

  • Error when editing network

    Getting the following error when trying to save changes to network:


  • Share Folder Permission Problem after installing new Docker

    Quote from jaytee1414

    Going through the folder on my mac shows portainer_data folder under volumes and also docker containers / images under the folder. (not changing anything just looking around. But to look around it it required me to change the folder permission to 777 (i know 777 is not secure at all so I changed to 755), which makes my first problem because it seems to also cause the web gui access of portainer to not work and I assume that OMV should provide enough permission at an automatic level that allows basic stuff such as portainer to work?

    I think here lies some of the confusion, there should be 0 need to look into the Docker folder, and it shouldn't be a shared drive your mac can access (can but no real need).

    Each Docker Container has its own config, and during the setup of the container you should be pointing it to an empty folder which the docker container can write too.

    Do this for each Container.

    This config then means whenever you restart the container, say to update it, the configuration is not lost.

    You can then add volumes to be able to access other files, such as videos.

  • OMV5 loses wifi connection

    Have you checked you are using the right firmware? Quite a few posts around that I read when trying to get my WiFi card working that older versions were quite unstable.

    Worth checking for updates.

  • Share Folder Permission Problem after installing new Docker

    Why are you trying to access the Docker folder? Depending on the what you're trying to run in Docker, usually you would share a folder with Docker and it would write to it and be able to access other things you put in there.

    Ie. E Plex, give it access to a movie folder for example. It can write as the Docker user (ie for renaming) and read as the movies were added under the "user" group.

    Don't think you should be messing with the Docker folder that is made when docker installs as you will have removed Portainers permissions to the same folder.

  • Share Folder Permission Problem after installing new Docker

    I've never had an issue with Docker messing with the permissions, usually just a case on ensuring when you are setting up the container you are providing it with an PGID and PUID to use that has appropriate permissions on the folders it is allowed to access.


    If the contaner makes files or folders, then that way they are created with the appropriate permissions.


    I usually make a user called docker, add it to a group called docker, but also add it to the users group so that any files created by the docker user are accessible via any user in the users group and vice versa