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
**Why should I run this image and not the other image(s) that already exist?** Good question! All the other images on the market that do exactly the same don’t do or offer these options:
22
+
**Why should I run this image and not the other image(s) that already exist?** Good question! Because ...
23
23
24
24
> [!IMPORTANT]
25
-
>*This image runs the proxy part as a specific UID/GID (not root), most other images run everything as root
26
-
>*This image uses a single binary, most other images use apps like Nginx or HAProxy (bloat)
27
-
>*This image has no shell since it is 100% distroless, most other images run on a distro like Debian or Alpine with full shell access (security)
28
-
>*This image does not ship with any critical or high rated CVE and is automatically maintained via CI/CD, most other images mostly have no CVE scanning or code quality tools in place
29
-
>*This image is created via a secure, pinned CI/CD process and immune to upstream attacks, most other images have upstream dependencies that can be exploited
30
-
>*This image contains a proper health check that verifies the app is actually working, most other images have either no health check or only check if a port is open or ping works
31
-
>*This image exposes the socket as a UNIX socket and TCP socket, most other images only expose it via a TCP socket
32
-
>*This image works as read-only, most other images need to write files to the image filesystem
25
+
>*... this image exposes the socket not as root but as 1000:1000
26
+
>*... this image has no shell since it is [distroless](https://github.com/11notes/RTFM/blob/main/linux/container/image/distroless.md)
27
+
>*... this image is auto updated to the latest version via CI/CD
28
+
>*... this image has a health check
29
+
>*... this image runs read-only
30
+
>*... this image is automatically scanned for CVEs before and after publishing
31
+
>*... this image is created via a secure and pinned CI/CD process
32
+
>*... this image is very small
33
33
34
-
If you value security, simplicity and the ability to interact with the maintainer and developer of an image. Using my images is a great start in that direction.
34
+
If you value security, simplicity and optimizations to the extreme, then this image might be for you.
35
35
36
36
# COMPOSE ✂️
37
37
```yaml
38
-
name: "traefik"
38
+
name: "reverse-proxy"
39
39
services:
40
40
socket-proxy:
41
-
image: "11notes/socket-proxy:2.1.3"
41
+
# this image is used to expose the docker socket as read-only to traefik
42
+
# you can check https://github.com/11notes/docker-socket-proxy for all details
43
+
image: "11notes/socket-proxy:2.1.4"
42
44
read_only: true
43
-
# make sure to use the same UID/GID as the owner of your docker socket!
44
-
user: "0:0"
45
+
user: "0:108"
46
+
environment:
47
+
TZ: "Europe/Zurich"
45
48
volumes:
46
-
# mount host docker socket, the :ro does not mean read-only for the socket, just for the actual file
### There is no latest tag, what am I supposed to do about updates?
121
-
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.3``` 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.
206
+
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.
122
207
123
208
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