While I don't agree w/ you about Yacht (I never could warm up to it).. Glad you got it working.
I've had a little more time in the saddle with Portainer vs Yacht and I retract my earlier statement about Yacht. 
Setting up new containers seems more straightforward with Portainer. It's a little closer to what I was used to in the OMV 4 UI.
Again, if all your paths, etc. remain unchanged. When you point the docker service at your old containers folder, all of your containers should "just work".
Thanks so much for your help! I was able to get my Dockers running after correctly setting my path(s).
I also had to create symlinks using the symlinks plugin so my existing Dockers would see their config files in their respective "AppData" directories. After all paths were added with symlinks, I decided to try Yacht as it looked easier to use and I don't need the extra functions in Portainer.
Yacht saw and started all my Dockers automatically. It did indeed "just work" as you said it would.
Thanks again!
I now see the path field is editable! It didn't appear so during installation.
Assume I'll need to reinstall Portainer after the path change. I'm wary of messing up the dockers in the directory.
Installing Portainer in the same directory shouldn't damage any of the existing dockers correct?
I have been running OMV 4 with several Dockers for years and finally decided to upgrade to OMV 6.
My current OMV 4 setup includes a USB flash drive for the OS, a couple data HDDs, and a HDD that my Dockers are installed to. The configs for the Docker applications are stored on one of my data hard drives in an AppData directory.
I clean installed OMV 6 to a new USB drive, mounted my HDDs, recreated same drive shares from OMV 4, installed OMV extras, Docker, and Portainer
I was hoping to migrate my dockers as they exist on their own HDD. My goal is to not have to reinstall and reconfigure the dockers. The path forward with Portainer wasn't as intuitive as I hoped.
Is it possible to add my existing Docker containers to Portainer and run them as they did on OMV 4?
I'm not near my NAS at the moment, but there should be. You might also want to make sure your configuration folders are being kept on the storage drives, if you've not done that yet. The config folders don't necessarily large usually, but they do a lot of disk writing with logs, etc..
I'm not saying any of this is your problem, as failing flash disks can give a myriad of strange warnings.. it's just something to think about.
I do have the docker configuration folders on the storage drive. Not thinking it all through correctly, my impression was that would prevent the writes to the OS disk. The failure on my part was not looking at the settings tab on the docker configuration. That would have shown me the option to install the dockers on my storage drive as well. Oops!
I agree... I really don't understand the infatuation w/ using flash drives (unless someone is out of SATA ports, at which point I'd probably still use an SSD to a usb header cable and put the SSD inside the case, if one is available). SSD prices have dropped pretty dramatically and finding SSD's in the 32-64gig range that support TRIM, is pretty easy. A buddy of mine who built his NAS used one of those cheap SSD's on Newegg, and used the flash plugin along with it... and that's been over a year and he's reported no problems at all. I use the flashplugin on a 64gig ADATA drive I picked up on sale on Amazon.. for going on 3yrs... no problems at all
The main reason I used a flash drive was indeed because the PC only has 4 SATA ports. I was also a long time FreeNAS user which recommends using a flash drive for the OS. I used plug-ins with FreeNAS and just didn't think much about the difference in dockers vs plug-ins and how it would affect my OS drive. 
As the saying goes; "once burned, twice learned."
Yes, I do apparently have my docker containers on my OS drive. I began to wonder about that and how much they would write to disk. 
For what it's worth, the flash drive was a new SanDisk cruiser model, so I felt fairly comfortable with it's reliability. Maybe undeservedly so? Is there a way to resolve my issue?
Is there a way to move my docker containers to another drive? Should I just concede that I need to rebuild with a real (larger) hard drive?
Thanks for your help.
I am running OMV4 from a 16GB USB flash drive (with flash memory plugin) on an old desktop PC. I have been running and testing for a couple weeks without too much issue. I have installed a few dockers and have been having a good time with it. Today, however, I ran into a curious error when checking for updates. When I check for updates, I am greeted with the error below:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update 2>&1' with exit code '135': Bus error
The more details button reveals:
Error #0:OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update 2>&1' with exit code '135': Bus error in /usr/share/openmediavault/engined/rpc/apt.inc:220Stack trace:#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMVRpcServiceApt->{closure}('/tmp/bgstatuskv...', '/tmp/bgoutputtO...')#1 /usr/share/openmediavault/engined/rpc/apt.inc(224): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))#2 [internal function]: OMVRpcServiceApt->update(NULL, Array)#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('update', NULL, Array)#5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Apt', 'update', NULL, Array, 1)#6 {main}
Unsure of what to do, I rebooted, but the error still remained. I then plugged my monitor in to try and run omv-firstaid from the command line, but could not and get the following error: print_req_error: crititcal medium error, dev sdb, sector 10613432
A bit of Google searching lead me to try running fsck on the drive while plugged into my main desktop machine. It found no errors.
Does the sector error indicate a USB drive that has gone bad? Please accept my apologies in advance for my ignorance. I'm fairly new to this.
Alles anzeigenI was able to get the docker setup and working. I was indeed configuring the network interface incorrectly. If you are using the default port you leave it in host mode and if you are needing to forward the port you use the Bridge; entering the IP of the machine in host IP, the new port in Host port and then select the application's port from the exposed ports.
I also did not have the container path setup correctly either. Once i realized that the default configurations paths show up if you just click in the container path box it made things much easier.
After configuring that I had to change a few settings in my guisettings.xml, advancedsettings.xml, and then upload my sources.xml from my other machine to get the library to start loading.
the linuxserver.io headless kodi doesn't have watchdog installed by default so I went into the userdata/plugins folder and copied the service.watchdog folder from a configured installation and dropped it into the userdata/plugins folder in the docker kodi. restarted kodi and went into the settings portion and watchdog appears in the settings. Turned it on and now it all works.
Now that i understand the actual mechanics of the docker plugin, setting up additional dockers is a piece of cake. I wish that with each plugin there would be a how to guide or a user manual to determine what the fields do, but it takes a lot of effort to develop and maintain so i get it. The docker plugin is pretty nice though and i really like it now that i get the setup steps.
Want to post a big thank you for posting your solution. If you hadn't posted, I never would have thought to try what you did. Thanks so much!
