Setup

Magento 2.4.x, Elastic Search 7.9.1 on Alpine Linux 3.12, jdk/bin/java: No such file or directory

While setting up a new local test environment specifically for Magento 2.4.x with Elastic Search on Alpine Linux ( Docker ) I had some problems with getting elastic search up and running.

# Use Alpine Linux
FROM alpine:3.12

# Other stuff

ENV ELASTICSEARCH_VERSION 7.9.1

RUN mkdir -p /opt/ && \
  cd /opt && \
  curl -Ls -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-$ELASTICSEARCH_VERSION-linux-x86_64.tar.gz && \
  tar -xvf elasticsearch-$ELASTICSEARCH_VERSION-linux-x86_64.tar.gz && \
  cd elasticsearch-$ELASTICSEARCH_VERSION/bin

# Use Alpine Linux

FROM alpine:3.12

# Other stuff

ENV ELASTICSEARCH_VERSION 7.9.1

RUN mkdir -p /opt/ && \

cd /opt && \

curl -Ls -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-$ELASTICSEARCH_VERSION-linux-x86_64.tar.gz && \

tar -xvf elasticsearch-$ELASTICSEARCH_VERSION-linux-x86_64.tar.gz && \

cd elasticsearch-$ELASTICSEARCH_VERSION/bin

The first issue I had was related to a missing home path of JAVA. Because of that, I wasn’t able to start Elastic Search at all.

bash-5.0# ./elasticsearch
./elasticsearch-env: line 77: /opt/elasticsearch-7.9.1/jdk/bin/java: No such file or directory

1 2	bash-5.0# ./elasticsearch ./elasticsearch-env: line 77: /opt/elasticsearch-7.9.1/jdk/bin/java: No such file or directory

I’ve fixed it by setting the missing path for JAVA_HOME which I have added later to my profile settings. https://stackoverflow.com/questions/35325856/where-to-set-system-default-environment-variables-in-alpine-linux

bash-5.0# which java
/usr/bin/java

1 2	bash-5.0# which java /usr/bin/java

export JAVA_HOME=/usr

1	export JAVA_HOME=/usr

The second issue was related to the JAVA version inside the docker container.

bash-5.0# ./elasticsearch
future versions of Elasticsearch will require Java 11; your Java version from [/usr/lib/jvm/java-1.8-openjdk/jre] does not meet this requirement

1 2	bash-5.0# ./elasticsearch future versions of Elasticsearch will require Java 11; your Java version from [/usr/lib/jvm/java-1.8-openjdk/jre] does not meet this requirement

Alpine Linux has the required version in the repository, which made it easy to install the missing package with apk.

bash-5.0# apk add openjdk11-jre
(1/2) Installing openjdk11-jre-headless (11.0.8_p10-r0)
(2/2) Installing openjdk11-jre (11.0.8_p10-r0)
Executing java-common-0.2-r0.trigger
OK: 649 MiB in 157 packages

bash-5.0# apk add openjdk11-jre

(1/2) Installing openjdk11-jre-headless (11.0.8_p10-r0)

(2/2) Installing openjdk11-jre (11.0.8_p10-r0)

Executing java-common-0.2-r0.trigger

OK: 649 MiB in 157 packages

Notice: Use of undefined constant T_CURLY_OPEN – assumed ‘T_CURLY_OPEN’ in /var/www/src/setup/src/ Magento/Setup/Module/ Di/Code/Reader/FileClassScanner.php on line 72

Today I finally had some time to cleaned up my Dockerfile for Magento 2. I am using Alpine Linux for most of my Magento 2 projects which usually includes NGINX, PHP-FPM and MariaDB.

# Use Alpine Linux
FROM alpine:3.7

# Declare maintainer
MAINTAINER Tobias Forkel <tobias@forkel.me>

# Timezone
ENV TIMEZONE Australia/Melbourne

RUN addgroup -g 1000 www && \
    adduser -S www -G www -s /sbin/nologin -D

ADD https://repos.php.earth/alpine/phpearth.rsa.pub /etc/apk/keys/phpearth.rsa.pub
RUN echo "https://repos.php.earth/alpine/v3.7" >> /etc/apk/repositories

RUN apk --no-cache add \
    bash \
    git \
	openssl \
	nginx \
	supervisor \
	curl \
	mariadb \
	mariadb-client \
	libxml2-utils \
	php7.1-common \
	php7.1-fpm \
	php7.1-json \
....

# Use Alpine Linux

FROM alpine:3.7

# Declare maintainer

MAINTAINER Tobias Forkel <tobias@forkel.me>

# Timezone

ENV TIMEZONE Australia/Melbourne

RUN addgroup -g 1000 www && \

adduser -S www -G www -s /sbin/nologin -D

ADD https://repos.php.earth/alpine/phpearth.rsa.pub /etc/apk/keys/phpearth.rsa.pub

RUN echo "https://repos.php.earth/alpine/v3.7" >> /etc/apk/repositories

RUN apk --no-cache add \

bash \

git \

openssl \

nginx \

supervisor \

curl \

mariadb \

mariadb-client \

libxml2-utils \

php7.1-common \

php7.1-fpm \

php7.1-json \

....

While testing my updated Dockerfile I came across the following PHP notice which prevented the deployment scripts from finishing the Magento 2 setup.

Notice: Use of undefined constant T_CURLY_OPEN - assumed 'T_CURLY_OPEN' in /var/www/src/setup/src/Magento/Setup/Module/ Di/Code/Reader/FileClassScanner.php on line 72

1	Notice: Use of undefined constant T_CURLY_OPEN - assumed 'T_CURLY_OPEN' in /var/www/src/setup/src/Magento/Setup/Module/ Di/Code/Reader/FileClassScanner.php on line 72

The problem was simply a missing PHP extension php7.1-tokenizer which has resolved the issue after re-creating the container with –build.

docker-compose up -d --build

1	docker-compose up -d --build

Change Order, Invoice, Credit Memo or Shipment Number Prefix or Suffix in Magento2

In some cases shop owners have to change their default order number with a custom prefix or suffix. Customising order numbers sounds complicated, but it can be done with only few MySQL queries.

First, backup your database. After that, get a list of meta_id’s and store_id’s with the following query for order numbers only.

SELECT * FROM sales_sequence_meta WHERE entity_type = 'order';

1	SELECT * FROM sales_sequence_meta WHERE entity_type = 'order';

+---------+-------------+----------+------------------+
| meta_id | entity_type | store_id | sequence_table   |
+---------+-------------+----------+------------------+
|       1 | order       |        0 | sequence_order_0 |
|       5 | order       |        1 | sequence_order_1 |
+---------+-------------+----------+------------------+
2 rows in set (0.00 sec)

+---------+-------------+----------+------------------+

+---------+-------------+----------+------------------+

| 1 | order | 0 | sequence_order_0 |

| 5 | order | 1 | sequence_order_1 |

+---------+-------------+----------+------------------+

2 rows in set (0.00 sec)

The meta_id is pretty much the identifier you need for the next UPDATE query which will add the letter A as a prefix. For example: A100000001

UPDATE sales_sequence_profile SET prefix = 'A' WHERE meta_id = 1;

1	UPDATE sales_sequence_profile SET prefix = 'A' WHERE meta_id = 1;

The same query can be used to change the suffix. Also, you can change the prefix or suffix for any entity_type such as invoice, creditmemo or shipment.

That’s it. Create a new order to see the results.

Reset Administrator User Password in Magento 2

Magento 2 comes with a CLI that allows you to create a new temporary administrator user within few seconds. Change to the directory where your Magento installation ( such as app or bin folder ) is located and run the following command to create a user support with password 8cd98f00b20.

php bin/magento admin:user:create --admin-user=support --admin-password=8cd98f00b20 --admin-email=support@myserver.com --admin-firstname=Firstname --admin-lastname=Lastname

1	php bin/magento admin:user:create --admin-user=support --admin-password=8cd98f00b20 --admin-email=support@myserver.com --admin-firstname=Firstname --admin-lastname=Lastname

Voilà!

Created Magento administrator user named support

1	Created Magento administrator user named support

Now you can go to System > Permissions > All Users and update other users credentials.