If you find Docker more difficult than FreeNas jails, there is no hope for you.
You don't have to run Portainer (if you're comfortable with command line).. it's just a lot of users find Portainer's GUI easy to use. Portainer should *NOT* be used to create containers, that's where stacks is far better, as you can just put a proper docker-compose file there, and edit as needed before deploying.
What exact problem are you having
I would say at minimum, 1000 and 100.. if he has not created a user, 1000 will not exist
I'm spending my evening re-reading the install pdf on OMV5 before doing anything else. But keep it coming....
Well one other thing I just noticed.. in the docker compose you posted earlier (with the 998 user), look at your first volume for /config. I'm assuming you need to put "emby" on the end of that path.
Is this a new install with no container data or are you trying to move containers that are already configured and working
OK, gotcha. I should keep it simple.
I added an edit to that post, but it should be noted that user is completely unprivileged without sudo access. Allowing that user sudo access would change my opinion
You'll end up using docker for something, just embrace it now. 
I don't use snapraid, but it seems you have everything in order to me.
Call that user something generic...ie Dockeradmin or Dockeruser I assume?
Some people create a specific user... i use my actual user... "ken"... who basically is my main user on the server... and just add him to the docker and SSH group as previously mentioned... I see no real need to create a user just for docker, since this user is completely unprivileged and does not have sudo access. Edit: One thing I failed to mention, when you go this route, you might also want to create a Home folder in the webUI (create folder in webUI ("Home"), Click Users, Click the Settings Tab, enable the trigger and choose "Home" from the drop down, Save)
It will keep you from getting some annoying quirks when using SSH as a user without a home directory.. but either way is fine.
Display MoreCreate a new user. Run your containers as that user. Add that user to the docker group.
Learn how to use docker run and docker create commands in the shell.
Make sure the permissions on any host volumes you use are such that the user that is running the container can access them to the degree necessary. It is IMPOSSIBLE to emphasize this enough. You shouldn't even start a container until you are sure of this first because this will bite you every single time. And the most frequently seen incorrect solution to this is to over relax the permissions.
Good luck.
Completely agree.
Permissions is exactly the reason I prefer doing everything as a user. I believe a lot of this is because so many tutorials, etc.. SSH as root and just start creating directories... and eventually it causes a problem for some users.
OK. I've been banging away this all day, and I'm in need of food and beer.
I am re-installing OMV5 from scratch, wiping drives, clean slate. I have no data on them so I lose nothing but install time. If you have any pointers that differ from the standard TDL or DBTech videos that make your OMVs more robust (No offense TDL, I know you are trying to make it simple), I'll gladly take them in the meantime (Since I hope to make this my last wipe & re-install).
I'll try and pick this up again tomorrow after work. Thank you for all your help. It was appreciated.
OK.... I'll be working tomorrow night... so I'll try to be as clear as possible.
After you reinstall run all updates (which doesn't sound like its necessary, but whatever toots your horn), etc, reinstall docker (if you're using a small OS drive, especially with Emby) make sure you set up your Containers folder on your storage drives (which I'm assuming are much larger than your OS drive).
Once you've reinstalled, and created your docker base folders (your containers folder, and AppData).. Create a user in the webUI of OMV. When you create this user, give the user a password, etc. At the bottom, change the shell to /bin/bash. Then in the new user window, click the Groups tab, and click the CHECKBOX (don't highlight it, there's a weird GUI bug that will uncheck everything on some browsers) next to SSH.
Save and Apply, your user should now show being in the users and ssh group.
Under SSH, restart the SSH server, and SSH in as your user.. not as root. Personally, I disable root SSH access, and always SSH as a user, and if I actually need to be root I just drop to root with the su - command.... but to each their own
cd to your AppData folder, and mkdir emby
Then use the stack I gave you above.
root@openmediavault:~# id admin
uid=998(admin) gid=100(users) groups=100(users),995(openmediavault-admin)
That make sense? I thought it was weird too.
I also might like TD & DB Techs videos, but I also think they're little sketchy security wise. That said, there's not a lot of youtube deep dives on doing it the hard & secure way.
It makes sense, but I wouldn't do it. As I said above, create a user, and then use a standard user to run the container.
containers & images gone. Can't delete my Config folder or its contents (Permission denied)
Use Root to delete it from command line, that is probably part of the problem, or set a new config path. I just deleted my emby path from my container w/ a regular user.
Display MoreYup. All following TDL, images are gone, but can't nuke my config folder. I'll try to delete it via OMV gui...
Here was my stack info if that helps point out where I went wrong. (P&UID info is as returned when I checked logging as root...maybe that or specifying TZ instead of local??)
---
version: "2.1"
services:
emby:
image: linuxserver/emby
container_name: emby
environment:
- PUID=998
- PGID=100
- TZ=America/Montreal
volumes:
- /srv/dev-disk-by-label-1TBD2/STORAG2/Config:/config
- /srv/dev-disk-by-label-2TBD1/MEDIA/TVShows:/data/tvshows
- /srv/dev-disk-by-label-2TBD1/MEDIA/Movies:/data/movies
ports:
- 8096:8096
restart: unless-stopped
Personally... I always bind /etc/localtime to /etc/local time, and don't set a TZ.. and then set it Read Only, so the container can't change my system time. This always keeps my containers, in sync w/ my system time. It has never caused me a problem.. but really either should work.
Where are you getting 998? Is that the admin user for the webUI? That's something dbtech does, and I like his videos, but I disagree w/ him on this (just as I disagree w/ TD doing every single thing he does as root). Create a user, and use that user, at least that is my opinion.
Otherwise, deploy it and see if it works
Clearly. What that is I'm not sure...followed TDL's youtube videos as usual.
OK, as I said above... delete your /config folder, delete your old container, etc. Then create a new /config folder (again, I'm assuming nothing here needs backed up)
Now, once you've done that... Open Portainer
On the left, click "Stacks"
Click Add New Stack
On the next window, Name the stack (emby)
Then Under "Web Editor" Paste all of this:
I'm assuming if you've used technodad videos the adjustments you need to make are obvious (PUID, PGID, etc.). MAKE SURE YOU ARE USING ABSOLUTE PATHS.
If you need a custom port, under ports, change the one on the "left" to your custom port.
Click deploy stack
I don't use Emby, but just for grins, I just set up the Linuxserver image w/ docker compose. Took barely 2min to set up and run, and I've already logged in to the emby UI.
OP is definitely doing something wrong.
I'm still on 4 and I have portainer installed, that recent update had no effect on any of my running containers and I can still use the plugin if I want too.
This really should work as well.
I've tried both emby official and the linuxserver.io images.
I've been to this rodeo before, last time I "upgraded" to OMV5. Same issues: spin up, go to webpage, get met with "forbidden". Reinstalled OMV4 and used the docker plugin. A recent update (of container.io I think) trashed all the dockers I had running (Emby, HomeAssistant Core, Heimdall, Lychee.) and crapped out the Docker plugin. Figured I should bite the bullet and try OMV5 again...and here I sit fighting with Portainer again.
and yes 64bit.
OK, so start w/ the easy part. I'm assuming since you mentioned all your dockers getting trashed, nothing needs backed up.
Delete your current emby container, delete the current /config folder you created, and if you're not using the linuxserver image... delete the image you're using. You can do all that in portainer. Then go ahead and create a new /config folder
There's that too. Also I want to stick with services that I assume to have more resources for setting up (youtube walkthroughs, etc.)
So... which image are you using?.. I'm assuming the linuxserver image and I'm assuming 64bit?
The media server choice is not the problem. It's the install method. Whatever I can't get past in Emby will be just as frustrating spinning up Jellyfin, or Plex.
Beyond that, I'm always suspect of using images from just random folks... Try to stick with well known image writers on dockerhub
I hear you. I have yet to succesfully get a single container running using Portainer on OMV5. The most frustrating experience I've had yet with Openmediavault. I think it's back to OMV4 for me.
That's kind of a silly way to go about it to be honest.
How are you attempting to set it up? and which emby image are you using.
I put my servers in a closet. I use a cable to connect to a USB port on the back side, and lay the drive on the top of the case. That makes for easy access for backup and nearly eliminates the possibility of breaking them.
There are a number of valid reasons to use an SSD to boot but I tend to push new users toward thumbdrive's for a number of reasons. Chief among them are, they're cheap so buying two is no big deal, and they're dirt simple to clone / back up.
Mine sits in a closet now. For a long time sat in the Living Room... and I was more paranoid about a particular someone just needing a flash drive and seeing it and saying, "Oh there's one". It would probably be OK nowadays.
Just out of sheer paranoia, I'd probably still use an internal header cable.
