Hi, i can confirm this issue on my server as well:
docker run -it owncloud/server:10.12.2@sha256:c62d824e1f70ef5262f68275e98c33f26978e2ae44f24da8d171ede18c1a65e2 occ -V
/usr/bin/occ: line 16: 15 Illegal instruction (core dumped) setpriv --reuid=www-data --regid=www-data --init-groups php /var/www/owncloud/occ "$@"
journalctl -e reports:
Aug 19 05:48:30 myserver kernel: traps: php[31358] trap invalid opcode ip:7f6978b19eed sp:7ffe2acbc220 error:0 in libMagickCore-7.Q16HDRI.so.10.0.1[7f69788e5000+284000]
When i run an older version, everything works as expected:
docker run -it owncloud/server:10.12.1@sha256:d9fe8fa11695d597f3de6a70e8d88529944b7e9077800c8d728f46859aaa3e22 occ -V
ownCloud is not installed - only a limited number of commands are available
ownCloud 10.12.1
(the container runs normally as well)
My theory is:
a few days ago, owncloud-docker/php/pull/131 was merged. This is introducing heic support (which i am looking forward to a lot by the way).
The new imagic 7 library is now freshly compiled in the docker build (instead of using the old ubuntu package as before) see: owncloud-docker/php/pull/131/files#diff-7bfcb8bd1ee62b4f198ae107d0f3bf9210ab9c3db14731f95957c7aa9af0e816R49
the imei.sh script is using the compiler arguments -march=native (see: SoftCreatR/imei/blob/main/imei.sh#L149) which is a good idea if you compile for your own hardware, but if you need to redistribute the built library (in a docker image) for other people with other CPUs to run on, this is problematic.
I think the docker image is built on relatively new CPUs and you and me have older CPUs. Our older CPUs cannot understand the new code shipped in the latest owncloud/server docker image.
Unfortunately, i do not know what the sha256 digest of the previous build was. (i whiped my server).
Does anyone have a x86 64-bit system with an older CPU where you can run the following listing?
docker images --digests
So i have owncloud/server:10.12.2@sha256:c62d824e1f70ef5262f68275e98c33f26978e2ae44f24da8d171ede18c1a65e2, which i know is not working on my CPU. Maybe someone has not updated yet, and has an older CPU as well. (so you have owncloud/server:10.12.1 but a different digest)
my lscpu is:
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz
CPU family: 6
Model: 76
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Stepping: 3
CPU max MHz: 2400,0000
CPU min MHz: 480,0000
BogoMIPS: 3200.00
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 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rd
rand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat md_clear
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 96 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 2 MiB (2 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Mitigation; Clear CPU buffers; SMT disabled
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec store bypass: Not affected
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
I would like to create an issue in the owncloud-docker/php project, if that is ok for the moderators (i do not know how things run in this community)
