Trying to install Appsmith in a Docker container on OSX but the installation stops at this point:
$ docker-compose up
[+] Running 1/0
⠿ Container appsmith Created 0.0s
Attaching to appsmith
appsmith | Initialize .env file
appsmith | Load environment configuration
appsmith | Checking environment configuration
appsmith | Checking APPSMITH_MONGODB_URI
appsmith | Detected local MongoDB
appsmith | Initializing local database
appsmith | '/appsmith-stacks/data/mongodb/key' -> '/mongodb-key'
appsmith | Checking initialized database
appsmith | Initializing Replica Set for local database
It works well on my Linux machine, but not on OSX using Docker version 20.10.22
Does anyone know what is causing this?
Can you please share the OS version, docker version, docker-compose version and the docker-compose.yml file.
Docker Compose version v2.15.1
Docker Desktop version 4.16.1
Docker Engine version 20.10.22
macOS Monterey version 12.6.2
Thanks in advance!
Can you also share your
Also, please send us the output of the following command to get more info about your CPU:
sysctl -a | grep machdep.cpu
The docker-compose.yml file has minimal changes from the stock version:
$ cat docker-compose.yml
# Uncomment the lines below to enable auto-update
# com.centurylinklabs.watchtower.enable: "true"
# image: containrrr/watchtower:latest-dev
# - /var/run/docker.sock:/var/run/docker.sock
# # Update check interval in seconds.
# command: --schedule "0 0 * ? * *" --label-enable --cleanup
# restart: unless-stopped
# - appsmith
# - WATCHTOWER_LIFECYCLE_HOOKS=true
The sysctl command yields this:
$ sysctl -a | grep machdep.cpu
machdep.cpu.brand_string: Apple M1 Pro
Sorry for the delay. Could you try running it again by changing the image field in the docker-compose to
Command to recreate container:
docker-compose up -d --force-recreate
Does this error have something to do with the upgrade do MongoDB 5? I can get AppSmith working on my Mac Mini M1 just fine with similar versions as @xsge, but not on my Synology. I’m guessing because MongoDB 5+ requires AVX support?
I believe you are running the container on docker desktop on your mac.
We were speculating that it could be due to the upgrade to mongo v5.0 supports the M1 arm processors.
You can use this calendy link below to schedule a call to debug this issue further.
Could you elaborate more on Synology, I believe it is a NAS right? Did you mean the Apsmith file system is mounted on the NAS?
Yes, mongov5.0 requires AVX support only in case of x86_64 processors but it does support the latest ARM processors which includes M1. You can refer to the MongoDB requirements here