You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,15 +70,13 @@ Mapping `docker.sock` is a potential security liability because docker has root
70
70
71
71
### Multiple Hosts
72
72
73
-
>[!NOTE]
74
-
>Make sure you fully understand what you're doing before you try and set this up as there are lots of ways it can go wrong if you're just guessing.
73
+
?+note[Security](|Make sure you fully understand what you're doing before you try and set this up as there are lots of ways it can go wrong if you're just guessing.|)
75
74
76
75
Modmanager can query & download mods for remote hosts, as well as the one on which it is installed. At a very basic level if you're just using the `DOCKER_MODS` env and not docker discovery, simply mount the `/modcache` folder on your remote host(s), ensuring it is mapped for all participating containers.
77
76
78
77
If you are using docker discovery, our only supported means for connecting to remote hosts is [our socket proxy container](https://github.com/linuxserver/docker-socket-proxy/). Run an instance on each remote host:
79
78
80
-
>[!WARNING]
81
-
>DO NOT expose a socket proxy to your LAN if it allows any write operations (`POST=1`, `ALLOW_RESTART=1`, etc) or exposes any API elements that are not absolutely necessary. NEVER expose a socket proxy to your WAN.
79
+
?+warning[Security](|DO NOT expose a socket proxy to your LAN if it allows any write operations (`POST=1`, `ALLOW_RESTART=1`, etc) or exposes any API elements that are not absolutely necessary. NEVER expose a socket proxy to your WAN.|)
82
80
83
81
```yml
84
82
modmanager-dockerproxy:
@@ -109,8 +107,7 @@ As above you will need to mount the `/modcache` folder on your remote host(s), e
109
107
110
108
To help you get started creating a container from this image you can either use docker compose or the docker cli.
111
109
112
-
>[!NOTE]
113
-
>Unless a parameter is flaged as 'optional', it is *mandatory* and a value must be provided.
110
+
?+note[Params](|Unless a parameter is flaged as 'optional', it is *mandatory* and a value must be provided.|)
114
111
115
112
### docker compose (recommended, [click here for more info](https://docs.linuxserver.io/general/docker-compose))
>We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
250
+
?+tip[Diun](|We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.|)
Copy file name to clipboardExpand all lines: readme-vars.yml
+4-8Lines changed: 4 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -74,15 +74,13 @@ full_custom_readme: |
74
74
75
75
### Multiple Hosts
76
76
77
-
>[!NOTE]
78
-
>Make sure you fully understand what you're doing before you try and set this up as there are lots of ways it can go wrong if you're just guessing.
77
+
?+note[Security](|Make sure you fully understand what you're doing before you try and set this up as there are lots of ways it can go wrong if you're just guessing.|)
79
78
80
79
Modmanager can query & download mods for remote hosts, as well as the one on which it is installed. At a very basic level if you're just using the `DOCKER_MODS` env and not docker discovery, simply mount the `/modcache` folder on your remote host(s), ensuring it is mapped for all participating containers.
81
80
82
81
If you are using docker discovery, our only supported means for connecting to remote hosts is [our socket proxy container](https://github.com/linuxserver/docker-socket-proxy/). Run an instance on each remote host:
83
82
84
-
>[!WARNING]
85
-
>DO NOT expose a socket proxy to your LAN if it allows any write operations (`POST=1`, `ALLOW_RESTART=1`, etc) or exposes any API elements that are not absolutely necessary. NEVER expose a socket proxy to your WAN.
83
+
?+warning[Security](|DO NOT expose a socket proxy to your LAN if it allows any write operations (`POST=1`, `ALLOW_RESTART=1`, etc) or exposes any API elements that are not absolutely necessary. NEVER expose a socket proxy to your WAN.|)
86
84
87
85
```yml
88
86
modmanager-dockerproxy:
@@ -113,8 +111,7 @@ full_custom_readme: |
113
111
114
112
To help you get started creating a container from this image you can either use docker compose or the docker cli.
115
113
116
-
>[!NOTE]
117
-
>Unless a parameter is flaged as 'optional', it is *mandatory* and a value must be provided.
114
+
?+note[Params](|Unless a parameter is flaged as 'optional', it is *mandatory* and a value must be provided.|)
118
115
119
116
### docker compose (recommended, [click here for more info](https://docs.linuxserver.io/general/docker-compose))
>We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
254
+
?+tip[Diun](|We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.|)
0 commit comments