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
+17-14Lines changed: 17 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,25 +163,24 @@ RUN npm run build
163
163
164
164
This image comes with 2 "types": the *slim* and the **fat** image.
165
165
166
-
The slim image contains only a set a base PHP extensions.
166
+
These extensions are enabled by default in slim image: `calendar``ctype``curl``date``dom``exif``fileinfo``filter``ftp``gettext``iconv``json``mbstring``opcache``openssl``pcntl``pcre``PDO``Phar``posix``readline``shmop``Reflection``session``shmop``SimpleXML``sockets``sodium``SPL``sysvmsg``sysvsem``sysvshm``tokenizer``xml``xmlreader``xmlwriter``xsl``zip`
167
167
168
-
Only these extensions are available in the slim image: `calendar``ctype``curl``dom``exif``fileinfo``ftp``gettext``iconv``json``mbstring``opcache``pcntl``pdo``phar``posix``readline``shmop``simplexml``sockets``sysvmsg``sysvsem``sysvshm``tokenizer``wddx``xml``xmlreader``xmlwriter``xsl``zip`
168
+
This list can be outdated, you can verify by executing : `docker run --rm -it thecodingmachine/php:8.0-v4-slim-cli php -m`
169
169
170
-
These extensions are enabled by default.
170
+
The slim image provides a simple way to install the other extensions. You would typically use the "slim" image in a `Dockerfile` when building your own custom image.
171
171
172
-
The slim image provides a simple way to install the other extensions. You would typically use the "slim"
173
-
image in a `Dockerfile` when building your own custom image.
174
-
175
-
The fat image contains the most commonly used extensions. You would typically use it in a local or CI environment.
172
+
The fat image contains the most commonly used extensions. You would typically use it in a local or CI environment.
176
173
177
174
### Fat image
178
175
179
176
Below is a list of extensions available in this image:
180
177
181
-
**Enabled by default (in addition to extensions enabled in Slim image):** apcu mysqli pdo_mysql igbinaryredissoap
178
+
**Enabled by default (in addition to extensions enabled in Slim image):**`apcu`, `hash`, `iconv`, `igbinary`, `mysqli`, `mysqlnd`, `redis`, `soap`, `xsl`, `zlib` and all enabled in slim.
182
179
183
180
**Available (can be enabled using environment variables):**`amqp``ast``bcmath``blackfire``bz2``dba``ds``enchant``ev``event``exif``mailparse``msgpack``gd``gettext``gmp``gnupg``grpc``igbinary``imagick``imap``intl``ldap``mcrypt``memcached``mongodb``pcov``pdo_dblib``pdo_pgsql``pdo_sqlite``pgsql``pspell``shmop``snmp``sockets``sqlite3``swoole``tidy``uploadprogress``uuid``weakref(-beta)``xdebug``xmlrpc``xsl``yaml`
184
181
182
+
This list can be outdated, you can verify by executing : `docker run --rm -it thecodingmachine/php:8.0-v4-cli php -m`
183
+
185
184
**Note**:
186
185
187
186
-*mcrypt* is not available anymore in PHP 7.3+
@@ -225,9 +224,11 @@ FROM thecodingmachine/php:8.0-v4-slim-apache
225
224
# of the extensions (thanks to a ONBUILD hook in the slim image)
226
225
```
227
226
228
-
Beware! The `ARG PHP_EXTENSIONS` command must be written before the `FROM`. This is not a typo.
229
-
230
-
**Heads up**: if you are using multistage builds, the "ARG" variable must be put at the very top of the file (before the
227
+
Beware :
228
+
* The `ARG PHP_EXTENSIONS` command must be written before the `FROM`. This is not a typo.
229
+
* `ARG PHP_EXTENSIONS=""` it's not the same as `ENV PHP_EXTENSIONS=""`
230
+
* You can't use `ARG PHP_EXTENSION_MYEXT=""` like the fat image.
231
+
* **Heads up**: if you are using multistage builds, the "ARG" variable must be put at the very top of the file (before the
231
232
first FROM):
232
233
233
234
```Dockerfile
@@ -346,9 +347,11 @@ As an alternative, you can use the `APACHE_EXTENSIONS` global variable:
Copy file name to clipboardExpand all lines: utils/README.blueprint.md
+17-14Lines changed: 17 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,25 +81,24 @@ RUN npm run build
81
81
82
82
This image comes with 2 "types": the *slim* and the **fat** image.
83
83
84
-
The slim image contains only a set a base PHP extensions.
84
+
These extensions are enabled by default in slim image: `calendar``ctype``curl``date``dom``exif``fileinfo``filter``ftp``gettext``iconv``json``mbstring``opcache``openssl``pcntl``pcre``PDO``Phar``posix``readline``shmop``Reflection``session``shmop``SimpleXML``sockets``sodium``SPL``sysvmsg``sysvsem``sysvshm``tokenizer``xml``xmlreader``xmlwriter``xsl``zip`
85
85
86
-
Only these extensions are available in the slim image: `calendar``ctype``curl``dom``exif``fileinfo``ftp``gettext``iconv``json``mbstring``opcache``pcntl``pdo``phar``posix``readline``shmop``simplexml``sockets``sysvmsg``sysvsem``sysvshm``tokenizer``wddx``xml``xmlreader``xmlwriter``xsl``zip`
86
+
This list can be outdated, you can verify by executing : `docker run --rm -it thecodingmachine/php:{{ $image.php_version }}-v4-slim-cli php -m`
87
87
88
-
These extensions are enabled by default.
88
+
The slim image provides a simple way to install the other extensions. You would typically use the "slim" image in a `Dockerfile` when building your own custom image.
89
89
90
-
The slim image provides a simple way to install the other extensions. You would typically use the "slim"
91
-
image in a `Dockerfile` when building your own custom image.
92
-
93
-
The fat image contains the most commonly used extensions. You would typically use it in a local or CI environment.
90
+
The fat image contains the most commonly used extensions. You would typically use it in a local or CI environment.
94
91
95
92
### Fat image
96
93
97
94
Below is a list of extensions available in this image:
98
95
99
-
**Enabled by default (in addition to extensions enabled in Slim image):** apcu mysqli pdo_mysql igbinaryredissoap
96
+
**Enabled by default (in addition to extensions enabled in Slim image):**`apcu`, `hash`, `iconv`, `igbinary`, `mysqli`, `mysqlnd`, `redis`, `soap`, `xsl`, `zlib` and all enabled in slim.
100
97
101
98
**Available (can be enabled using environment variables):**`amqp``ast``bcmath``blackfire``bz2``dba``ds``enchant``ev``event``exif``mailparse``msgpack``gd``gettext``gmp``gnupg``grpc``igbinary``imagick``imap``intl``ldap``mcrypt``memcached``mongodb``pcov``pdo_dblib``pdo_pgsql``pdo_sqlite``pgsql``pspell``shmop``snmp``sockets``sqlite3``swoole``tidy``uploadprogress``uuid``weakref(-beta)``xdebug``xmlrpc``xsl``yaml`
102
99
100
+
This list can be outdated, you can verify by executing : `docker run --rm -it thecodingmachine/php:{{ $image.php_version }}-v4-cli php -m`
101
+
103
102
**Note**:
104
103
105
104
-*mcrypt* is not available anymore in PHP 7.3+
@@ -143,9 +142,11 @@ FROM thecodingmachine/php:{{ $image.php_version }}-v4-slim-apache
143
142
# of the extensions (thanks to a ONBUILD hook in the slim image)
144
143
```
145
144
146
-
Beware! The `ARG PHP_EXTENSIONS` command must be written before the `FROM`. This is not a typo.
147
-
148
-
**Heads up**: if you are using multistage builds, the "ARG" variable must be put at the very top of the file (before the
145
+
Beware :
146
+
* The `ARG PHP_EXTENSIONS` command must be written before the `FROM`. This is not a typo.
147
+
* `ARG PHP_EXTENSIONS=""` it's not the same as `ENV PHP_EXTENSIONS=""`
148
+
* You can't use `ARG PHP_EXTENSION_MYEXT=""` like the fat image.
149
+
* **Heads up**: if you are using multistage builds, the "ARG" variable must be put at the very top of the file (before the
149
150
first FROM):
150
151
151
152
```Dockerfile
@@ -264,9 +265,11 @@ As an alternative, you can use the `APACHE_EXTENSIONS` global variable:
0 commit comments