The Basics
- I run Nextcloud Hub 25 Autumn (32.0.4) using Nextcloud AIO v12.5.0
Summary of the issue you are facing:
When enabling the community container “Local AI”, it remains stuck during startup
Steps to replicate it:
-
Enable communit container and restart Nextcloud.
-
Persists also after disabling and enabling Local AI again.
Log entries
2026-01-29T19:43:10.253736960Z CPU info:
2026-01-29T19:43:10.255296720Z model name : 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
2026-01-29T19:43:10.255900333Z 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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx avx512f avx512dq rdseed adx smap avx512ifma clflushopt intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid fsrm md_clear flush_l1d arch_capabilities
2026-01-29T19:43:10.256555276Z CPU: AVX found OK
2026-01-29T19:43:10.257073923Z CPU: AVX2 found OK
2026-01-29T19:43:10.257573134Z CPU: AVX512 found OK
2026-01-29T19:43:10.264221217Z nc: getaddrinfo for host "nextcloud-aio-nextcloud" port 9001: Temporary failure in name resolution
2026-01-29T19:43:10.264283768Z Waiting for nextcloud to start
2026-01-29T19:43:15.266963831Z Waiting for nextcloud to start
2026-01-29T19:43:20.268893269Z Waiting for nextcloud to start
2026-01-29T19:43:25.270928088Z Waiting for nextcloud to start
2026-01-29T19:43:30.272738701Z Waiting for nextcloud to start
2026-01-29T19:43:35.274452992Z Waiting for nextcloud to start
2026-01-29T19:43:40.286111417Z Waiting for nextcloud-aio-local-ai/models.yaml file to be created
2026-01-29T19:43:45.286602867Z Waiting for nextcloud-aio-local-ai/models.yaml file to be created
2026-01-29T19:43:50.287364670Z Waiting for nextcloud-aio-local-ai/models.yaml file to be created
2026-01-29T19:43:55.288086776Z Waiting for nextcloud-aio-local-ai/models.yaml file to be created
2026-01-29T19:44:00.288937203Z Waiting for nextcloud-aio-local-ai/models.yaml file to be created
2026-01-29T19:44:05.289652919Z Waiting for nextcloud-aio-local-ai/models.yaml file to be created
…keeps logging this… I was waiting more than 48 hrs without success… 
Some output of docker commands:
~ ❯❯❯ sudo docker inspect nextcloud-aio-local-ai | grep nextcloud
"Name": "/nextcloud-aio-local-ai",
"nextcloud_aio_localai_models:/models:rw",
"nextcloud_aio_localai_images:/tmp/generated/images/:rw",
"/mnt/data/nextcloud_data:/nextcloud:ro"
"NetworkMode": "nextcloud-aio",
"Name": "nextcloud_aio_localai_models",
"Source": "/var/lib/docker/volumes/nextcloud_aio_localai_models/_data",
"Source": "/mnt/data/nextcloud_data",
"Destination": "/nextcloud",
"Name": "nextcloud_aio_localai_images",
"Source": "/var/lib/docker/volumes/nextcloud_aio_localai_images/_data",
"Hostname": "nextcloud-aio-local-ai",
"com.docker.compose.project": "nextcloud-aio",
"nextcloud-aio": {
"nextcloud-aio-local-ai",
~ ❯❯❯ sudo docker inspect nextcloud-aio-nextcloud | grep Network
"NetworkMode": "nextcloud-aio",
"NetworkSettings": {
"Networks": {
"NetworkID": "SOME_LONG_UNIQUE_ID--same-as-below"
~ ❯❯❯ sudo docker inspect nextcloud-aio-local-ai | grep Network
"NetworkMode": "nextcloud-aio",
"NetworkSettings": {
"Networks": {
"NetworkID": "SOME_LONG_UNIQUE_ID--same-as-above"
Any idea how to fix this? Any feedback would be appreciated. 