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
Access your docker socket safely as read-only, rootless and distroless
7
7
@@ -48,9 +48,7 @@ If you value security, simplicity and optimizations to the extreme, then this im
48
48
name: "reverse-proxy"
49
49
services:
50
50
socket-proxy:
51
-
# this image is used to expose the docker socket as read-only to traefik
52
-
# you can check https://github.com/11notes/docker-socket-proxy for all details
53
-
image: "11notes/socket-proxy:2.1.6"
51
+
image: "11notes/socket-proxy:2.1.7"
54
52
read_only: true
55
53
user: "0:0"
56
54
environment:
@@ -61,6 +59,8 @@ services:
61
59
restart: "always"
62
60
63
61
traefik:
62
+
# for more information about this image checkout:
63
+
# https://github.com/11notes/docker-traefik
64
64
depends_on:
65
65
socket-proxy:
66
66
condition: "service_healthy"
@@ -153,7 +153,8 @@ services:
153
153
restart: "always"
154
154
155
155
errors:
156
-
# this image can be used to display a simple error message since Traefik can’t serve content
156
+
# for more information about this image checkout:
157
+
# https://github.com/11notes/docker-postgres
157
158
image: "11notes/traefik:errors"
158
159
read_only: true
159
160
labels:
@@ -167,6 +168,8 @@ services:
167
168
168
169
# example container
169
170
nginx:
171
+
# for more information about this image checkout:
172
+
# https://github.com/11notes/docker-nginx
170
173
image: "11notes/nginx:stable"
171
174
read_only: true
172
175
labels:
@@ -194,7 +197,7 @@ networks:
194
197
backend:
195
198
internal: true
196
199
```
197
-
To find out how you can change the default UID/GID of this container image, consult the [how-to.changeUIDGID](https://github.com/11notes/RTFM/blob/main/linux/container/image/11notes/how-to.changeUIDGID.md#change-uidgid-the-correct-way) section of my [RTFM](https://github.com/11notes/RTFM)
200
+
To find out how you can change the default UID/GID of this container image, consult the [RTFM](https://github.com/11notes/RTFM/blob/main/linux/container/image/11notes/how-to.changeUIDGID.md#change-uidgid-the-correct-way).
198
201
199
202
# ENVIRONMENT 📝
200
203
| Parameter | Value | Default |
@@ -207,26 +210,27 @@ To find out how you can change the default UID/GID of this container image, cons
207
210
| `SOCKET_PROXY_GID` | the GID used to run the proxy parts | 1000 |
### There is no latest tag, what am I supposed to do about updates?
217
-
It is of my opinion that the ```:latest``` tag is dangerous. Many times, I’ve introduced **breaking** changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest [semver](https://semver.org/), simply use the short versions of [semver](https://semver.org/). Instead of using ```:2.1.6``` you can use ```:2``` or ```:2.1```. Since on each new version these tags are updated to the latest version of the software, using them is identical to using ```:latest``` but at least fixed to a major or minor version.
221
+
It is my opinion that the ```:latest``` tag is a bad habbit and should not be used at all. Many developers introduce **breaking changes** in new releases. This would messed up everything for people who use ```:latest```. If you don’t want to change the tag to the latest [semver](https://semver.org/), simply use the short versions of [semver](https://semver.org/). Instead of using ```:2.1.7``` you can use ```:2``` or ```:2.1```. Since on each new version these tags are updated to the latest version of the software, using them is identical to using ```:latest``` but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.
218
222
219
223
If you still insist on having the bleeding edge release of this app, simply use the ```:rolling``` tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the [releases](https://github.com/11notes/docker-socket-proxy/releases) for breaking changes. If you have any problems with using this image simply raise an [issue](https://github.com/11notes/docker-socket-proxy/issues), thanks. If you have a question or inputs please create a new [discussion](https://github.com/11notes/docker-socket-proxy/discussions) instead of an issue. You can find all my other repositories on [github](https://github.com/11notes?tab=repositories).
0 commit comments