In extend to my previous post :https://lemmy.ml/post/22320175

I cannot install drupal 11 on a fresh Debian install, in fact I tried everything and it's no more the fault of proxmox, but the PHP installation.

Drupal 11 needs php 8.3 to work, but Debian official repos go only to php 8.2, so I used the sury.org Debian repo to install the latest PHP version. And this is the start of the problem, this install gives me the error shown in the other post, exhausted memory.

I search in the info.php, memory related stuff, and the only difference between the "official" PHP (8.2) and sury one is that in the mysqldn section it shows statistics to yes. But I don't know how to disable it...

Any ideas? Thanks 😉

all 17 comments

sorted by: hot top controversial new old
[–] 3 points 2 years ago (3 children)

I wanted to recommend using a Docker container but I ran into the same issue with the default config for "drupal:10-apache" (aka "drupal:10.3.7-apache-bookworm"). Opening "node/add/article" results in the OOM error. Downgrading to "drupal:10.3.6-apache-bookworm" resolved the issue. Looks like a Drupal regression to me. Maybe you can also try an older version of Drupal 11?

  • source
  • hideshow 6 child comments
  • [–] 2 points 2 years ago (1 child)

    "11.0.5-apache-bookworm" also seems to work, maybe you can try that version?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago (1 child)

    So you think it's the fault of drupal 11, not the PHP repo?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    Yes, the docker images don't use the sury.org php packages (they use the php docker image).

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago (1 child)

    Can you please send a link of the docker image, don't know if it's the good one that I found

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago

    I used the docker compose template from https://hub.docker.com/_/drupal and mostly changed the image:

    Compose file

    # Drupal with PostgreSQL
    #
    # Access via "http://localhost:8080"
    #   (or "http://$(docker-machine ip):8080" if using docker-machine)
    #
    # During initial Drupal setup,
    # Database type: PostgreSQL
    # Database name: postgres
    # Database username: postgres
    # Database password: example
    # ADVANCED OPTIONS; Database host: postgres
    
    version: '3.1'
    
    services:
    
      drupal:
        # image: drupal:10-apache
        # image: drupal:10.3.7-apache-bookworm
        # image: drupal:10.3.6-apache-bookworm
        image: drupal:11.0.5-apache-bookworm
        # image: drupal:10-php8.3-fpm-alpine
        ports:
          - 8080:80
        volumes:
          - /var/www/html/modules
          - /var/www/html/profiles
          - /var/www/html/themes
          # this takes advantage of the feature in Docker that a new anonymous
          # volume (which is what we're creating here) will be initialized with the
          # existing content of the image at the same location
          - /var/www/html/sites
        restart: always
        environment:
          PHP_MEMORY_LIMIT: "1024M"
    
      postgres:
        image: postgres:16
        environment:
          POSTGRES_PASSWORD: example
        restart: always
    
    

    The details for the v11 image are here: https://hub.docker.com/layers/library/drupal/11.0.5-apache-bookworm/images/sha256-0e41e0173b4b5d470d30e2486016e1355608ab40651549e3e146a7334f9c8f77?context=explore

  • source
  • parent
  • [–] 2 points 2 years ago (1 child)

    Did the 8.3 replace official repo 8.2 or does it use different naming for php binaries? The config files might be separate too.

    Try using phpinfo() to check your working config. You can just place a file with the function in the root of your webserver and it should work.

    It seems like the memory allowance is too low for drupal to load.

  • source
  • hideshow 2 child comments
  • [–] [S] 1 point 2 years ago

    In fact when using PHP from sury.org the PHP 8.3 is available in addition to PHP 8.2. When using the phpinfo() and comparing the two PHP versions the only difference related a bit to memory are the statistics that are turned on. Nothing really more

  • source
  • parent
  • [–] -1 points 2 years ago (1 child)

    Is there a reason for creating a new thread? For example have you stopped trying to use proxmox or other virtual environments to get it working?

  • source
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago* (1 child)

    This is why I made a new thread because the error is not coming from anything else than the php repo of sury.org, no more a "self-hosted" or Linux proxmox issue.

    EDIT : tried the same install in KVM and on my desktop, it's not working. Tried Debian 10 with official PHP and it's working

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago* (1 child)

    So just to be clear, you're trying to install Drupal 11 on your system OS which is Debian?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 1 point 2 years ago (1 child)

    I want to install it on a Debian VM inside promox, but to eliminate the potential issues, I tried to install it inside KVM on host, and on a other PC which is running Debian as host. When installing drupal 11 I needed PHP 8.3 so I used the sury.org repo, and I think it the main problem. Because when installing drupal 10 with "official" Debian PHP (8.2) it works.

  • source
  • parent
  • hideshow 2 child comments