Root password ending on '\J' causes a crash

When creating an instance of the mysql:5.7 container, with the following variables from an env file (using docker compose):

root@demo01:/conf/docker# cat envfile.env | grep 'MYSQL'
MYSQL_DATABASE=somevalue
MYSQL_USER=sqluser
MYSQL_PASSWORD=(6T+B\`2@`Bf]cqF
MYSQL_ROOT_PASSWORD=;*{q#'Br9+qxh2\J
MYSQL_ROOT_HOST=%

MySQL crashes with the following output in the log:

Initializing database
2019-06-15T15:23:59.415039Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-06-15T15:24:00.127942Z 0 [Warning] InnoDB: New log files created, LSN=45790
2019-06-15T15:24:00.250132Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2019-06-15T15:24:00.310568Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 99a9caa4-8f81-11e9-acf7-0242ac140002.
2019-06-15T15:24:00.311781Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2019-06-15T15:24:00.312706Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
Database initialized
Initializing certificates
Generating a RSA private key
.................................................................+++++
.................................................................................+++++
unable to write 'random state'
writing new private key to 'ca-key.pem'
-----
Generating a RSA private key
...........+++++
..........................................+++++
unable to write 'random state'
writing new private key to 'server-key.pem'
-----
Generating a RSA private key
.........................................................................+++++
................+++++
unable to write 'random state'
writing new private key to 'client-key.pem'
-----
Certificates initialized
MySQL init process in progress...
2019-06-15T15:24:06.640728Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-06-15T15:24:06.648939Z 0 [Note] mysqld (mysqld 5.7.26) starting as process 89 ...
2019-06-15T15:24:06.674792Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-06-15T15:24:06.674827Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-15T15:24:06.674838Z 0 [Note] InnoDB: Uses event mutexes
2019-06-15T15:24:06.674849Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-06-15T15:24:06.674859Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-06-15T15:24:06.674870Z 0 [Note] InnoDB: Using Linux native AIO
2019-06-15T15:24:06.675462Z 0 [Note] InnoDB: Number of pools: 1
2019-06-15T15:24:06.675674Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-06-15T15:24:06.691483Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-06-15T15:24:06.751571Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-06-15T15:24:06.765430Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-06-15T15:24:06.779958Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-15T15:24:06.813040Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-06-15T15:24:06.817139Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-06-15T15:24:06.906716Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-06-15T15:24:06.909770Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-06-15T15:24:06.909789Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-06-15T15:24:06.910300Z 0 [Note] InnoDB: Waiting for purge to start
2019-06-15T15:24:06.960487Z 0 [Note] InnoDB: 5.7.26 started; log sequence number 2524985
2019-06-15T15:24:06.961302Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-06-15T15:24:06.967999Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2019-06-15T15:24:06.971097Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190615 15:24:06
2019-06-15T15:24:06.988611Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2019-06-15T15:24:06.990031Z 0 [Warning] CA certificate ca.pem is self signed.
2019-06-15T15:24:07.003237Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2019-06-15T15:24:07.067563Z 0 [Note] Event Scheduler: Loaded 0 events
2019-06-15T15:24:07.068076Z 0 [Note] mysqld: ready for connections.
Version: '5.7.26'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server (GPL)
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping it.
ERROR at line 5: Unknown command '\J'.

Reproduce the issue by creating a mysql:5.7 container with the shown Docker Compose environment file and a MYSQL_ROOT_PASSWORD ending in \J. Check the initialization output for the Unknown command error, and consider the issue done when the container initializes successfully with that password.