plausible docker image support for linux/arm/v7? Raspberry PI 4

[1mfaasj]

I want to deploy plausible on a raspberry pi 4 with docker compose (selfhosted) but can't get it to work. It seems that the image 'plausible/analytics:' is not made for raspberry. can this be correct?
I also have tried 'plausible/analytics:v1.5.0-rc.1' but it not working either.

the error message is:
failed to deploy a stack: plausible Pulling no matching manifest for linux/arm/v7 in the manifest list entries
my docker compose contains:

version: "3.3"
services:
  plausible_db:
    image: postgres:12
    volumes:
      - /srv/dev-disk/blabla/plausible/db:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=postgres
    restart: always

  plausible_events_db:
    image: altinity/clickhouse-server:21.12.3.32.altinitydev.arm
    volumes:
      - /srv/dev-disk/blabla/plausible/events:/var/lib/clickhouse
    ulimits:
      nofile:
        soft: 262144
        hard: 262144

  plausible:
    image: plausible/analytics
    command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
    depends_on:
      - plausible_db
      - plausible_events_db
#      - mail
    ports:
      - 8000:8000
    environment:
#      - [email protected]
#      - ADMIN_USER_NAME=admin
#      - ADMIN_USER_PWD=password
      - BASE_URL=https://mywebsite.com
      - SECRET_KEY_BASE=BLABLABLA
    restart: always

[ruslandoga]

@jboesh 👋

That's right, we are currently building only for arm64 (armv8) and amd64 -- the archs that https://hub.docker.com/r/clickhouse/clickhouse-server (one of the bigger dependencies) is built for.

However, a bit of googling is showing me that raspberry pi 4 is armv8 so you might want to check why raspberry pi os is thinking it's armv7.

[Athep]

docker inspect plausible-ce-plausible_events_db-1

{
"Status": "restarting",
"Running": true,
"Paused": false,
"Restarting": true,
"OOMKilled": false,
"Dead": false,
"Pid": 0,
"ExitCode": 132,
"Error": "",
"StartedAt": "2025-01-23T19:44:42.82917883Z",
"FinishedAt": "2025-01-23T19:44:45.527200987Z",
"Health": {
"Status": "unhealthy",
"FailingStreak": 0,
"Log": []
}

[ruslandoga]

Oh, that's very useful! 132 means illegal instruction. That's what #2555 (reply in thread) is about. I guess you'll need to build your own ClickHouse image or just run it outside of Docker.

Here's what ChatGPT suggests for a Dockerfile

---

Full reply: https://chatgpt.com/share/6792b7b1-b6f8-8010-bf0a-2b95ff08b538

# Use a minimal base image
FROM debian:bullseye-slim

# Set environment variables to avoid interactive prompts
ENV DEBIAN_FRONTEND=noninteractive

# Install required packages
RUN apt-get update && apt-get install -y \
    curl \
    ca-certificates \
    && apt-get clean && rm -rf /var/lib/apt/lists/*

# Install ClickHouse
RUN curl https://clickhouse.com/ | sh

# Expose the default ClickHouse HTTP port
EXPOSE 8123

# Expose the default ClickHouse TCP port
EXPOSE 9000

# Set ClickHouse server as the default command
CMD ["clickhouse-server"]

---

[Athep]

Thank you.

I have only limited experience with Linux, but I will try.

FYI, there is a similar analytics "umami" that runs without any issues on my RPi4B.

[ruslandoga]

I haven't used Umami but it seems like a good choice, especially if it already works :)

[Athep]

I prefer Plausible and would like to get it working. Umami is also running in docker. Very similar.