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
@@ -50,9 +50,9 @@ services:
50
50
socket-proxy:
51
51
# this image is used to expose the docker socket as read-only to traefik
52
52
# you can check https://github.com/11notes/docker-socket-proxy for all details
53
-
image: "11notes/socket-proxy:2.1.4"
53
+
image: "11notes/socket-proxy:2.1.5"
54
54
read_only: true
55
-
user: "0:108"
55
+
user: "0:0"
56
56
environment:
57
57
TZ: "Europe/Zurich"
58
58
volumes:
@@ -194,6 +194,7 @@ networks:
194
194
backend:
195
195
internal: true
196
196
```
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)
197
198
198
199
# ENVIRONMENT 📝
199
200
| Parameter | Value | Default |
@@ -210,18 +211,18 @@ networks:
210
211
# MAIN TAGS 🏷️
211
212
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
### There is no latest tag, what am I supposed to do about updates?
216
-
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.4``` 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.
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.5``` 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.
217
218
218
219
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