Search Results

Search results 1-20 of 242.

  • I know about TABs @macom I work a lot with CLI But as I saw on different guides for docker-compose some are mixing the paths. Like /srv/dev-disk-by-label/xxx and /sharedfolders/xxx I read somewhere that paths with /srv/dev-xxx should be more stable than /sharedfolders/xxxx @draddy I know what symlinks are but didn't work with it. I also didn't know about the plugin (shame on me). What I do with my containers and compose-files is to copy them. So when I do a fresh installation, I create the same …

  • Quote from KM0201: “If you use filesystem labels, ” Sorry, what do you understand by that. Would you be so kind and post an example. Thanks in advance

  • @Gst wie @draddy schrieb, ohne deine compose-file ist es nur raten mit der Glaskugel.

  • Plugins that are wanted - Part 5

    Huberer - - Plugins

    Post

    Quote from ryecoaaron: “there had only been a few commits ” Sorry, I didn't check the commits. I've just had a look at the date of the last chance. So I can't say how active this repo is. But I will check KVM anyway. This is an official repo so why not to try. Thanks for the hint on that

  • Plugins that are wanted - Part 5

    Huberer - - Plugins

    Post

    Quote from ryecoaaron: “plus phpvirtualbox isn't really actively maintained anymore. ” I guess yes. You can see it here that updates are still made. You're right the repo for the virtualbox is a one man show. It's not fix if there're updates in the future or not.

  • Plugins that are wanted - Part 5

    Huberer - - Plugins

    Post

    @ryecoaaron Thanks. I know that OMV is not an OS. OMV is just a GUI for Debian Server. This is what I learned for sure in the last years I've installed virtualbox via CLI and it was very easy to install. I saw that Virtualbox is not in the Debian repos and I also read why. But with adding the repos it was very easy. I also found that someone is supporting an unofficial repo for Virtualbox for Debian 10. I also could install the extension pack but, than came phpvirtualbox. That was really terribl…

  • Plugins that are wanted - Part 5

    Huberer - - Plugins

    Post

    Hello, is there a chance to get Virtualbox working under OMV v5? It looks like that this is the first "Server OS" without the possibility to run virtual machines besides OMV (except by using ESXI - which I really don't know how it works). OMV v4 with the Virtualbox Plugin was great. I really loved it. Maybe there's a chance to get Virtualbox running under OMV v5. Thanks in advance

  • Installation on fresh Debian 9 fails

    Huberer - - General

    Post

    Which version of Debian 9 did you use for installation. I did it several times and didn't face any problems. I used this version for basis installation. At the end when you have to choose which packages to install I only ticked "ssh server" and "standard system utilities". You don't need more. Don't install a GUI like Xfce .... After the the first login with root (I install the server with a keyboard/mouse and screen attached) I enabled root. After that I reboot the server again. And then I conn…

  • @gderf After I've posted my thread I checked my two installations files for docker (normal docker and docker-compose) and realized that there were backslash. I removed it and installed everything new and voila docker-compose used the config-folder of the .yml-file. Thanks anyway for the hint. The issus is now solved.

  • Hello, with OMV v4 I was running a lot of docker containers without any problems. Now, after the upgrade (to OMV v5) I decided to switch from normal docker to docker compose. Therefore I've installed docker and portainer via omv-extras. Furthermore I've updated to the latest docker-compose via CLI (according to GitHub). My first docker-compose installation was Plex Media Server. Therefore I've created this docker-compose.yml: Source Code (19 lines)Under the OMV-GUI I've changed the docker storag…

  • Thanks I will do that. I will stay with the standard-kernel and use docker like they should

  • So today I did a fresh installation of Debian 10 again (yesterday I did an UEFI-installation and today a MBR-installation) and OMV via CLI. The problem remains. Portainer isn't working with Proxmox-kernel but with the standard kernel without any problems. Now I've the question. What is better: To stay with the standard-kernel and install the docker containers like they should or use the proxmox-kernel (newer and better stability) and install the docker containers with privileged mode? Thanks in …

  • Quote from MightyMo: “I'm going to try the --privileged flag now.” This shouldn‘t be done because with this flag you have full access to all files and folders (security risk). Running all containers with privileged mode is not a good option. Gesendet von iPad mit Tapatalk

  • @ryecoaaron How do you log in the OMV-GUI? Via root or admin? Mayby admin doesn‘t have the proper rights to run portainer. The container folder under var has root-privileges and admin doesn‘t have access to it. I‘ve forgotten to test but maybe adding admin to the docker-group can solve this issue. Gesendet von iPad mit Tapatalk

  • Quote from ryecoaaron: “Did you change the docker path? I don’t and portainer has always worked fine without the privileged flag. ” No, I didn't. As I wrote before, with the standard kernel everything is ok. Only problems with the proxmox kernel. forum.openmediavault.org/index…6bf0316517c9cf803192f95a6 The next problem is that I have created a Plex container (docker compose) but it also doesn't start. Till I found out by adding the privileged option (mode) Plex started as normal. It looks like t…

  • Quote from ryecoaaron: “I doubt this line is causing the problem. I'm guessing the volume has corrupt data in it. I would remove portainer from the web interface and the delete the volume (docker volume rm portainer_data). Then I would re-install from the web interface. ” I did a fresh installation of Debian 10 on my system drive. Before I formatted the drive with zeros to be sure everything is "clean". I did this kind of installation twice but the problem with Portainer still remains. Somewhere…

  • OMV 4.x Or OMV 5.x on Debian 10.2?

    Huberer - - General

    Post

    Quote from KM0201: “ OMV isn't designed to run alongside a GUI. ” With my "old" system (OMV v4) I had installed Xfce besides OMV (the base install was Debian 9 and afterwards I've installed OMV). I didn't face any problems with this system - Debian 9 with Xfce and OMV (side by side). This system was running around one year without any hassles. With my "new" system (OMV v5 on Debian 10) I plan to do the same.

  • Quote from ryecoaaron: “I just rebooted to see if that changed anything and it is still working fine ” Really curious. Here on my system (signature) it's not working. In the evening I will try to install Portainer by hand to see where the problem is.

  • I have the same problem with Portainer. With standard-kernel (4.19) everything runs fine but with Proxmox-kernel v5.3.13-2-pve (latest one) Portainer keeps restarting everytime (by installing via omv-extras). @ryecoaaron As I can see in your signature you're using the Proxmox-kernel too, aren't you? Is Portainer working on your setup (with Proxmox kernel)? Do you have any clue why Portainer is not working with the Proxmox kernel?

  • Portainer: Much Ado About Nothing

    Huberer - - Docker

    Post

    Come back to the problem of Squeezebox. Squeezebox needs internal (inside docker) the 9000 port and portainer too. Could it be a problem of installing both even you change their external ports? How should docker know to which container the connection should go. For me it looks like that both programs are listing at the same port. How should that work? Am I right or do I think completely wrong?