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
+22-18Lines changed: 22 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,6 @@ Find us at:
14
14
*[Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
15
15
*[Podcast](https://anchor.fm/linuxserverio) - on hiatus. Coming back soon (late 2018).
16
16
17
-
# PSA: Changes are happening
18
-
19
-
From August 2018 onwards, Linuxserver are in the midst of switching to a new CI platform which will enable us to build and release multiple architectures under a single repo. To this end, existing images for `arm64` and `armhf` builds are being deprecated. They are replaced by a manifest file in each container which automatically pulls the correct image for your architecture. You'll also be able to pull based on a specific architecture tag.
20
-
21
-
TLDR: Multi-arch support is changing from multiple repos to one repo per container image.
[](https://microbadger.com/images/linuxserver/mariadb"Get your own version badge on microbadger.com")
@@ -35,7 +29,7 @@ TLDR: Multi-arch support is changing from multiple repos to one repo per contain
35
29
36
30
## Supported Architectures
37
31
38
-
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).
32
+
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
39
33
40
34
Simply pulling `linuxserver/mariadb` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
41
35
@@ -57,8 +51,8 @@ Here are some example snippets to help you get started creating a container.
57
51
```
58
52
docker create \
59
53
--name=mariadb \
60
-
-e PUID=1001 \
61
-
-e PGID=1001 \
54
+
-e PUID=1000 \
55
+
-e PGID=1000 \
62
56
-e MYSQL_ROOT_PASSWORD=<DATABASE PASSWORD> \
63
57
-e TZ=Europe/London \
64
58
-p 3306:3306 \
@@ -80,15 +74,14 @@ services:
80
74
image: linuxserver/mariadb
81
75
container_name: mariadb
82
76
environment:
83
-
- PUID=1001
84
-
- PGID=1001
77
+
- PUID=1000
78
+
- PGID=1000
85
79
- MYSQL_ROOT_PASSWORD=<DATABASE PASSWORD>
86
80
- TZ=Europe/London
87
81
volumes:
88
82
- <path to data>:/config
89
83
ports:
90
84
- 3306:3306
91
-
mem_limit: 4096m
92
85
restart: unless-stopped
93
86
```
94
87
@@ -99,8 +92,8 @@ Container images are configured using parameters passed at runtime (such as thos
99
92
| Parameter | Function |
100
93
| :----: | --- |
101
94
|`-p 3306`| Mariadb listens on this port. |
102
-
|`-e PUID=1001`| for UserID - see below for explanation |
103
-
|`-e PGID=1001`| for GroupID - see below for explanation |
95
+
|`-e PUID=1000`| for UserID - see below for explanation |
96
+
|`-e PGID=1000`| for GroupID - see below for explanation |
104
97
|`-e MYSQL_ROOT_PASSWORD=<DATABASE PASSWORD>`| Set this to root password for installation (minimum 4 characters). |
105
98
|`-e TZ=Europe/London`| Specify a timezone to use EG Europe/London. |
106
99
|`-v /config`| Contains the db itself and all assorted settings. |
@@ -111,11 +104,11 @@ When using volumes (`-v` flags) permissions issues can arise between the host OS
111
104
112
105
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
113
106
114
-
In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as below:
107
+
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
0 commit comments