Failed to start: container ix-nextcloud-nextcloud-1 is unhealthy

[Pete_Dubler]

Trying a new install of Nextcloud from Truenas Apps with Truenas as a VM in Proxmox.

I get this in /var/log/app_lifecycle.log

Waiting\n Container ix-nextcloud-nextcloud-1  
Error\ndependency failed to start: container ix-nextcloud-nextcloud-1 is unhealthy\n

messages on pop-up at end of install:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
    await self.future
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 562, in __run_body
    rv = await self.middleware.run_in_thread(self.method, *args)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 599, in run_in_thread
    return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 596, in run_in_executor
    return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 294, in nf
    rv = func(*args, **kwargs)
         ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py", line 96, in wrapped
    result = func(*args)
             ^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 148, in do_create
    return self.create_internal(job, app_name, version, data['values'], complete_app_details)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 193, in create_internal
    raise e from None
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 186, in create_internal
    compose_action(app_name, version, 'up', force_recreate=True, remove_orphans=True)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/compose_utils.py", line 61, in compose_action
    raise CallError(err_msg)
middlewared.service_exception.CallError: [EFAULT] Failed 'up' action for 'nextcloud' app. Please check /var/log/app_lifecycle.log for more details

Exported and saved my TrueNas config tar.
I shutdown the Proxmox server, disconnected my TrueNAS RAID disks, restarted the server, removed the Truenas VM and created it anew.
Next shutdown, reconnected the disks, and assigned the disks.
Went to Truenas via web page, general, uploaded my backed up config and confirmed that my datasets were correct.
Truenas/Apps, install NextCloud.
and end up with the same error.

Do I need to restore ix-nextcloud-nextcloud-1 and if so, where is it and how can I restore it? If a whole reinstall does not do it, what am I missing?

Thanks!

[vawaver]

From my perspective, this setup is unnecessarily complex and introduces layers that only make things more fragile and harder to manage.
Running Nextcloud as an app inside TrueNAS Scale, which itself runs as a virtual machine on Proxmox, doesn’t make much sense in terms of reliability and maintainability.

This kind of architecture:

• reduces overall stability,
• makes troubleshooting difficult (where exactly is the problem — TrueNAS, Nextcloud, Docker?),
• and adds performance overhead — especially for disk and network I/O.

If you’re already using Proxmox, the most straightforward and stable solution is:
→ a dedicated VM running a Linux server with Nextcloud AIO.
(I also wouldn’t recommend using an LXC container in this case, since Nextcloud AIO runs Dockers inside, and Dockers inside LXC can lead to compatibility issues.)

TrueNAS definitely has its strengths — it’s a great NAS or network storage backend via NFS or iSCSI.
But in this setup, it becomes just another layer that introduces unnecessary complexity.

---

Just to sum it up: this kind of multi-layered architecture might seem attractive at first glance, but in practice, it often brings more issues than benefits.
I’ve found that keeping things simple works best — either use TrueNAS as your NAS, or run Nextcloud as a standalone solution.
Trying to combine both in a single stack usually results in harder maintenance and increased risk of failure.

---

Note: This post was written with the help of an AI assistant as a writing aid only. The opinions, solutions, and technical recommendations are fully based on my personal experience.
More about how and why I use AI to write forum posts:
Is there limitations to installing Nextcloud via CT template on Proxmox - #4 by vawaver

[Pete_Dubler]

@vawaver, thanks for the perspective. I appreciate that perspective. It is also interesting that a lot of people have recommended exactly the configuration I am using and that Nextcloud is a featured add-on within the TrueNas scale distribution.
Since I already have Truenas in a VM and trust it to maintain my data, this stack seems logical to expand the functionality without starting all over again.
My problem is not about the stability of either TrueNas or Nextcloud but rather comes down to a mistake I must have made in deleting the prior Nextcloud installation which is preventing me from reinstalling it.

That returns me to my original question… what directory got clobbered and where can I find a copy to restore it?

[Pete_Dubler]

close this request.