Posts by shazster

    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

    I'm spending my evening re-reading the install pdf on OMV5 before doing anything else. But keep it coming....

    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.

    OK, gotcha. I should keep it simple.

    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.

    Call that user something generic...ie Dockeradmin or Dockeruser I assume?

    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.

    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

    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.

    Yup. 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

    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.

    Clearly. What that is I'm not sure...followed TDL's youtube videos as usual.

    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

    containers & images gone. Can't delete my Config folder or its contents (Permission denied)

    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'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.

    Beyond that, I'm always suspect of using images from just random folks... Try to stick with well known image writers on dockerhub

    There's that too. Also I want to stick with services that I assume to have more resources for setting up (youtube walkthroughs, etc.)

    Emby container log if thats of any help. Any other logs I should post?



    Info App: Loading MediaBrowser.Model, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading MediaBrowser.Common, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading MediaBrowser.Controller, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Providers, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Photos, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Server.Implementations, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.LiveTV, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.ActivityLog, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Server.MediaEncoding, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.LocalMetadata, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Notifications, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Codecs.Dxva, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Codecs, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Server.Connect, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading Emby.Server.Sync, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info App: Loading EmbyServer, Version=4.5.0.50, Culture=neutral, PublicKeyToken=null,

    Info SqliteUserRepository: Sqlite version: 3.32.3,

    Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-8.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1,

    Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal,

    Info AuthenticationRepository: Default journal_mode for /config/data/authentication.db is wal,

    Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal,

    Info SqliteDisplayPreferencesRepository: Default journal_mode for /config/data/displaypreferences.db is wal,

    Info App: Adding HttpListener prefix http://+:8096/,

    Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal,

    Info Skia: SkiaSharp version: 2.80.0.0,

    Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 09/28/2020 02:00:00, which is 601.0041506766667 minutes from now.,

    Info TaskManager: Daily trigger for Rotate log file set to fire at 09/28/2020 00:00:00, which is 481.003878235 minutes from now.,

    Info App: ServerId: 7727e62d9d71428bae232d0aeca54280,

    Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint,

    Info Dlna: Registering publisher for urn:schemas-upnp-org:device:MediaServer:1,

    Info App: Init BeginReceive on 0.0.0.0,

    Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.1006606 seconds,

    Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint,

    Info App: Loading data from /config/data/connect.txt,

    Info App: Loading data from /config/data/wan.dat,

    Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0053686 seconds,

    Info App: Core startup complete,

    Info App: Post-init migrations complete,

    Info App: Starting entry point NfoMetadata.EntryPoint,

    Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0003836 seconds,

    Info App: Starting entry point Emby.Security.PluginSecurityManager,

    Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 3.49E-05 seconds,

    Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint,

    Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0001 seconds,

    Info App: Starting entry point Emby.Webhooks.WebhooksEntryPoint,

    Info App: Entry point completed: Emby.Webhooks.WebhooksEntryPoint. Duration: 0.0019192 seconds,

    Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding,

    Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0004747 seconds,

    Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint,

    Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 5.97E-05 seconds,

    Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint,

    Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0009593 seconds,

    Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistsEntryPoint,

    Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistsEntryPoint. Duration: 0.000835 seconds,

    Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint,

    Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.0001309 seconds,

    Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint,

    Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0003797 seconds,

    Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup,

    Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.1746784 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0001969 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0001432 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0014875 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier,

    Info LibraryMonitor: Watching directory /data/movies,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0021966 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0003334 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0003276 seconds,

    Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier,

    Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 8.96E-05 seconds,

    Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint,

    Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0019422 seconds,

    Info App: Starting entry point Emby.LiveTV.EntryPoint,

    Info LiveTV: Loading live tv data from /config/data/livetv/timers,

    Info LibraryMonitor: Watching directory /data/tvshows,

    Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0180793 seconds,

    Info App: Starting entry point Emby.LiveTV.LiveTVEntryPoint,

    Info App: Entry point completed: Emby.LiveTV.LiveTVEntryPoint. Duration: 0.0001534 seconds,

    Info App: Starting entry point Emby.LiveTV.RecordingNotifier,

    Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0018652 seconds,

    Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint,

    Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0027324 seconds,

    Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint,

    Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0013624 seconds,

    Info App: Starting entry point Emby.Notifications.Notifications,

    Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0002452 seconds,

    Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint,

    Info App: SyncRepository Initialize taking write lock,

    Info App: SyncRepository Initialize write lock taken,

    Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0036072 seconds,

    Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint,

    Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0016258 seconds,

    Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint,

    Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 9.14E-05 seconds,

    Info App: All entry points have started,

    Instead EMBY, you can try Jellyfin. It is the same service with all free, (opensource).

    You can download this docker image: linuxserver/jellyfin.


    You will find also an Android Client in Play Store.

    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.

    I suggest not using Portainer at all for bring up new containers. It's OK for managing them once they are created. Use docker run, docker create, or docker compose commands in the shell instead. If you insist on using Portainer, paste a proper docker compose file into a new stack.

    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.

    Is there a decent howto or walkthrough to get Emby set up on OMV5 via Portainer that DOES NOT result in me staring at a webpage that says "Forbidden" or should I just dump OMV5 for OMV4 and go back to what actually works? This is my 2nd go at an OMV5 setup and am rapidly running out of patience with Portainer as a vehicle for spinning up local services.

    I have a dual ethernet intel based network card, only using one port, set to a client side static IP, one cable. Nothing plugged into the other port.

    Is setting up a bonded IP using both ports the way to go (or the only option), or can my currently unused ethernet port/connection be pressed into service to provide connectivity to a currently running Docker exclusively? Say for Emby (in Docker) or HomeAssistant (in Docker) traffic? Can it be dedicated exculsively to something running in virtuabox?

    Yup.

    What you are running is HomeAssistant Core. It does not include the overall OS that allows you to run the add-ons -essentially their own Docker implementation.

    They seem to really pushing everyone towards raspberry pi installs, and not everyone is content with that platform (As neither of us probably are...hence why you and I are both here on an OMV forum...)

    Thanks. I've given up on it too. Migrated my logitech Audio serving to Daphile running on an old Atom mini pc. Clears room for another stab at HomeAssistant Core in Docker on my OMV.
    Would have liked to have it all in one, but keeping my tunes separate is fine, and I'm really warming up to Daphile to handle my LMS needs.

    non-Portainer related LMSinOMV question for original poster:
    I have LMS running in Docker in OMV4...runs fine with the exception that 3rd party LMS plugins crap out on me (chromecast & Airplay support - I think it may be a permissions issue or folder issue or docker binding issue ie. The xml config file that LMS creates to hold plugin info seems unaccessable. Do you use 3rd part LMS plugins and if so are they working OK?

    Ok. I see it there.
    So the shared folder where it will reside is on a data drive, and can be created using the normal OMV web GUI, & the install script should point the install to there.
    And is OMV's Shell in a Box plugin terminal adequate inputting the script?