Skip to content
Back

appwrite/appwrite:1.7.4 image missing Entrypoint and Apache not running

  • 0
  • Self Hosted
Ab
25 Jul, 2025, 15:18

Hi Team, I'm experiencing a critical issue when deploying the official appwrite/appwrite:1.7.4 Docker image.

After pulling the image (both by tag and by digest), I verified the configuration with: docker inspect appwrite/appwrite:1.7.4 | grep Entrypoint And the result is: "Entrypoint": [ There is no actual value — the Entrypoint is empty, which appears to be preventing the new Sites feature from routing correctly.

I also checked: docker inspect appwrite/appwrite:1.7.4 | grep RepoDigests And the RepoDigests field is also empty, suggesting this image may not have come from Docker Hub properly or was mispublished.

Inside the running container: docker exec -it appwrite sh ps aux | grep apache Returns: 44 root 0:00 grep apache

Which confirms Apache is not running at all.

My understanding is that Apache is responsible for handling incoming HTTP requests and routing them internally within Appwrite. Is it correct to assume that if Apache is not running, the Sites feature will not route correctly or respond at all?

Despite multiple clean pulls, docker rmi, re-pulls by digest, and even attempts to bypass the cache, the image remains broken.

Can you please confirm:

  • Whether appwrite/appwrite:1.7.4 has a valid Entrypoint in the latest Docker Hub image?
  • Whether this image may have been overwritten or misconfigured after its original publish?

Docker version: 26.1.5 Pull method: docker pull appwrite/appwrite:1.7.4 + digest

TL;DR
Developers experiencing issues with the appwrite/appwrite:1.7.4 Docker image. Entrypoint missing, Apache not running, leading to 404 errors on Sites feature. Docker inspection shows empty Entrypoint and RepoDigests fields. Apache not running in the container. Suspect mispublished image. Request confirmation on correct image state.
Steven
25 Jul, 2025, 15:21

How did you run/deploy Appwrite?

Ab
25 Jul, 2025, 15:24

Thanks for the quick response!

I deployed Appwrite using Docker Compose inside a Dokploy-managed environment. The Appwrite service is defined in the docker-compose.yml and runs alongside other core containers like appwrite/console, appwrite/browser, mariadb, and redis.

Specifically: Appwrite version: appwrite/appwrite:1.7.4 Deployed via: Dokploy

Docker Compose is handling the startup of the Appwrite container All required volumes (/storage/...) are mounted

Traefik is used as the reverse proxy, configured with wildcard routing for Sites (*.domain.com) _APP_DOMAIN_SITES=domain.com is correctly set

After deployment, the main container is running, but the Entrypoint is missing and Apache does not start — causing Appwrite to return 404 page not found for Sites.

Please let me know if you'd like me to share the docker-compose.yml snippet or more about the Dokploy configuration.

Steven
25 Jul, 2025, 15:27

Where did you get the compose file? Can you share it?

Ab
25 Jul, 2025, 15:42

I copied the compose file from the Appwrite GitHub repo and modified it a bit to make it work with Dokploy. The dokploy-network label is automatically added by Dokploy.

I also tested adding these labels to try to get Appwrite Sites working with wildcard routing: traefik.http.routers.appwrite-sites.rule=HostRegexp({subdomain:[a-z0-9-]+}.domain.com) traefik.http.routers.appwrite-sites.entrypoints=websecure traefik.http.routers.appwrite-sites.tls.certresolver=letsencrypt traefik.http.services.appwrite-sites.loadbalancer.server.port=80 traefik.http.routers.appwrite-sites.service=appwrite-sites

Here’s the full compose file I’m using right now

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more