Installed SAB container through online guide, What does this mean? Is this ok? 8181:8080 - 9191:9090

stevedawg85 · 15. Dezember 2021

stack - https://gist.github.com/dnburgess/e00fc05a567f278828ff72b3e35ed3cc

I'm following along dbtech youtube video, and he referenced the above stack. I hurdled over a few obstacles, but now have it up and running but with a question. Sab has ports 8181:8080 - 9191:9090. In my sonarr I had to configure the connection to use 8181, but in SAB when I review port info, it's listed as 8080. Make sense?

Generally speaking what does this mean? Sonarr has 8989:8989 & radarr 7878:7878 which looks more common or makes more sense to me.

chente · 15. Dezember 2021

I don't know how to answer the question, I don't use those containers. The only thing that caught my attention was the use of user 998 (admin, I think I remember). I would not, it is safer to create a user for docker with more restricted permissions.

gderf · 15. Dezember 2021

External (host side) port:Internal (container side) port.

You can not run containers with the same host side port simultaneously, it will result in a conflict and the conflicting container will not start.

Also, it's not a good idea to change the container side port number. These can not conflict so they can be reused.

From the stack you cited, using PGID=998 is not a good idea.

stevedawg85 · 16. Dezember 2021

I'm switching topics to the concern you both brought up regarding pgid. Tell me if I did this correctly?:

1. Stopped Stack

2. Created new user, userapp, with SSH & Sudo access (is this ok?)

3. Edit stack & updated w/ pgid to that of userapp

4. Shared Folders > /config folder > ACL > Extra Options: Change Owner = userapp & RWE, Group = users & RWE, Others = RWE, Replace & Recurisve (I want userapp to have access to this entire config area right, this correct?)

5. Start Stack

Followup question which might trigger a separate forum topic/discussion, now what to do for userapp to have access to my /data folder. Similar to step 4, but for the /data folder?

Note to self: found this guide earlier today, seems helpful, going off that - [How to] Prepare OMV to install docker applications

chente · 16. Dezember 2021

Zitat von stevedawg85

1. Stopped Stack
2. Created new user, userapp, with SSH & Sudo access (is this ok?)
3. Edit stack & updated w/ pgid to that of userapp
4. Shared Folders > /config folder > ACL > Extra Options: Change Owner = userapp & RWE, Group = users & RWE, Others = RWE, Replace & Recurisve (I want userapp to have access to this entire config area right, this correct?)
5. Start Stack

Followup question which might trigger a separate forum topic/discussion, now what to do for userapp to have access to my /data folder. Similar to step 4, but for the /data folder?

Alles anzeigen

You shouldn't need to use ACL permissions. Just add the user to the docker group (as the guide you found says). By default this user should already be in the users group (although I am not sure if it is OMV6, make sure of this. Then you must grant userapp access to the folders defined as volumes on each stack.

If a folder has access for group users, then userapp already has access, because it belongs to that group.

Take a look at this. https://wiki.omv-extras.org/do…d=nas_permmissions_in_omv

Jetzt mitmachen!