wekan: Latest MongoDB images require AVX instructions - Debian VMs fail to run
Issue
After the latest update the mongodb image keeps restarting complaining about AVX instructions.
Server Setup Information
- Did you test in newest Wekan?: YES
- Did you configure root-url correctly so Wekan cards open correctly (see https://github.com/wekan/wekan/wiki/Settings)? YES
- Operating System: Debian
- Deployment Method (Snap/Docker/Sandstorm/bundle/source): Docker
- Http frontend if any (Caddy, Nginx, Apache, see config examples from Wekan GitHub wiki first): Nginx reverse proxy to localhost:port
- Node.js Version: the one provided in Docker image
00478f580306 - MongoDB Version: latest Docker image, commit
ee13a1eacac9 - What webbrowser version are you using (Wekan should work on all modern browsers that support Javascript)? Irrelevant (Ferdi App)
/etc/os-release:
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
uname -a:
Linux <hostname> 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
docker image ls: (before and after today’s update)
REPOSITORY TAG IMAGE ID CREATED SIZE
wekanteam/wekan latest 00478f580306 35 hours ago 558MB
mongo latest ee13a1eacac9 2 weeks ago 696MB
wekanteam/wekan <none> 95ab2d50c8f5 13 months ago 638MB
mongo <none> 3068f6bb852e 13 months ago 493MB
Problem description
After the latest update (today) the wekandb container is continously restarting with the following error message:
$ docker compose logs
wekan-db | WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
wekan-db | see https://jira.mongodb.org/browse/SERVER-54407
wekan-db | see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2
wekan-db | see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814
Reproduction Steps
- Download / copypaste the
docker-compose.ymlin a Debian Buster virtual machine (at least this is my setup) - Run the compose stack (I have compose v2, tho it should not matter)
- Fail
Logs
The wekan image is working but cannot connect to the database, the wekandb logs are provided above.
Proposed solution
Either:
- Document this thing somewhere where stupid users like me who just run
apt update && apt upgrade -ycan reference something and know what’s actually going on before digging through GitHub issues and Jira tickets and all that good stuff - Default to MongoDB 4.x something (or at least for now), which is what I’m gonna do right now
- Both the above 🤷🏻
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 28 (17 by maintainers)
A thread talking about CPU instruction sets and having to compiling your own database. For a Kanban board. 😄
@timdonovanuk, have you tried to build mongodb without sandy bridge optimizations? For example, as in this patch: https://github.com/GermanAizek/mongodb-without-avx
@xet7, if you need a Dockerfile then here it is https://github.com/GermanAizek/mongodb-without-avx/blob/main/Dockerfile
@razum2um
Your question moved to https://github.com/wekan/wekan/issues/4578#issuecomment-1407769397
Or, should I fork MongoDB, and remove AVX code? 😉
@willman42
Does Qemu support emulating AVX ? 😉