Rank 1: Thread
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