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
If you are using 3rd Party modules which are not available on the FHEM svn repository, you may need this image, because it has more perl modules preinstalled.
36
50
37
51
To let this image work correctly, you need as least a FHEM revision 25680 or newer.
38
52
39
-
##### Not updated anymore since Jan 2024
53
+
##### Version 3 - EOL Jan 2024
40
54
41
55
- debian buster
42
56
- Perl 5.28.1
@@ -53,7 +67,23 @@ To let this image work correctly, you need as least a FHEM revision 25680 or new
If you are using only modules which are provided via FHEM svn repository, you mostly can use this smaller image.
83
+
84
+
##### Version 4 - EOL Jan 2025
85
+
86
+
- debian bullseye
57
87
- Perl 5.36.3 (optional threaded)
58
88
- Python 3.9.2
59
89
- Python 2.7.18
@@ -64,7 +94,7 @@ To let this image work correctly, you need as least a FHEM revision 25680 or new
64
94
65
95
If you are using only modules which are provided via FHEM svn repository, you mostly can use this smaller image.
66
96
67
-
##### Not updated anymore since Jan 2024
97
+
##### Version 3 - EOL Jan 2024
68
98
69
99
- debian buster
70
100
- Perl 5.28.1
@@ -77,7 +107,7 @@ If you are using only modules which are provided via FHEM svn repository, you mo
77
107
78
108
#### To start your container right away:
79
109
80
-
docker run -d --name fhem -p 8083:8083 ghcr.io/fhem/fhem-docker:4-bullseye
110
+
docker run -d --name fhem -p 8083:8083 ghcr.io/fhem/fhem-docker:5-bookworm
81
111
82
112
#### Storage
83
113
Usually you want to keep your FHEM setup after a container was destroyed (or re-build) so it is a good idea to provide an external directory on your Docker host to keep that data:
0 commit comments