Support

I have a feeling this problem may be down to your Docker configuration. Here's what I tried.

First, I created a Joomla 4.4 installation following the Docker Composer instructions in https://hub.docker.com/_/joomla/ i.e. creating the following compose.yaml file (note the image I am using):

services:
  joomla:
    image: joomla:4-php8.1-apache
    restart: always
    ports:
      - 9898:80
    environment:
      JOOMLA_DB_HOST: db
      JOOMLA_DB_USER: joomla
      JOOMLA_DB_PASSWORD: 2Yypqqv4a3V5DGShCYJfP8DvRbVqQgqd
      JOOMLA_DB_NAME: joomla_db
      JOOMLA_SITE_NAME: Joomla
      JOOMLA_ADMIN_USER: Super Duper
      JOOMLA_ADMIN_USERNAME: admin
      JOOMLA_ADMIN_PASSWORD: CAv6yeycY9VtxA53s9XhbyDz3mABq7sp
      JOOMLA_ADMIN_EMAIL: [email protected]
    volumes:
      - joomla4_data:/var/www/html
    networks:
      - joomla4_network

  db:
    image: mysql:8.0
    restart: always
    environment:
      MYSQL_DATABASE: joomla_db
      MYSQL_USER: joomla
      MYSQL_PASSWORD: 2Yypqqv4a3V5DGShCYJfP8DvRbVqQgqd
      MYSQL_RANDOM_ROOT_PASSWORD: '1'
    volumes:
      - joomla4_db:/var/lib/mysql
    networks:
      - joomla4_network

volumes:
  joomla4_data:
  joomla4_db:

networks:
  joomla4_network:

I started this up with docker compose up.

Since we have a Docker volume, we have to use docker cp to copy files into it. I opened a terminal window and run the following (note that ab15c60446078f470f019010b0a0346834a6d90d68387726c63aeb446014aaad is the ID of the Joomla container created when I ran docker compose up):

cd /path/to/my/local/directory
docker cp site.jpa ab15c60446078f470f019010b0a0346834a6d90d68387726c63aeb446014aaad:/var/www/html/site.jpa
docker cp kickstart.php ab15c60446078f470f019010b0a0346834a6d90d68387726c63aeb446014aaad:/var/www/html/kickstart.php

I then accessed http://localhost:9898/kickstart.php and proceeded to extract the backup and finish the restoration. I had no trouble with the installer.

The problem with the installed getting stuck, however, reminds me of something that was a problem in version 10.0.2 but fixed in 10.0.3. So, I am wondering. Could it be Joomla not fully updating the extension? In the meantime, we have version 10.0.4.

So, let's try this. Install 10.0.4 twice in a row, without uninstalling it before or in between. Take a new backup of your site, and try restoring that into your Docker setup. If that works, the problem was a half-updated Akeeba Backup; it's rare, but it happens. If that didn't work, the problem is with your Docker configuration. Most likely you are using a mount instead of a volume, and the permissions on the mount don't allow PHP to create new files / directories – or at least installation/tmp is unwritable. This would cause the restoration script to freeze as it can't move forward without a writeable storage space (a file in the installation/tmp directory) for its session.

The error says "Article not found". This means that Joomla cannot find the article in the database. Can you log into the backend of the site and make sure the menu item is set up correctly, and that the article you are trying to access exists, and has the right access level?

Hm, how about replacing the contents of the .htaccess file with those of the htaccess.txt file that comes with Joomla?