Good evening,
I’m using Docker Desktop on Windows as well as Docker on Debian and Ubuntu.
Up to last week I was running a MongoDB-server (version 4.4.6) with success on all my machines (1x Windows, 1x Debian, 1x Ubuntu).
Now I tried to switch to mongo:latest which was successful on the Windows-machine and the Debian-machine but not on the Ubuntu-machine - it exits/restarts every some seconds with status 132.
After checking with Google it seems that my older Ubuntu-notebook is missing sse4_2-support as seen on the following (partial - only for one of the two cores) output of cat /proc/cpuinfo
processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz stepping : 10 microcode : 0xa0b cpu MHz : 985.009 cache size : 3072 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority dtherm ida bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 4788.27 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
I am using the following docker-compose.yml
version: '3.1'
services:
mongo:
image: mongo:latest
restart: unless-stopped
ports:
- 27017:27017
environment:
MONGO_INITDB_ROOT_USERNAME: ***
MONGO_INITDB_ROOT_PASSWORD: ***
network_mode: bridge
volumes:
- data:/data/db
volumes:
data:
Yeah, I know that I should not use :latest-images - but IMHO it is OK in a test-environment - that is what test-environments are for :-).
So I have to buy a new Notebook for testing when every other docker-image in use (nginx, php:7.4-fpm, redis, mysql, mariadb, node:current-alpine, memcached, postgres, …) is starting flawless?
Or is it something the creators of the official mongodb-docker-image can do?
Thank you and best regards
Matthias