Containerized Nextcloud & Owncloud

I've been using Nextcloud for several years.  I prefer Owncloud but Owncloud, IMO, is pretty arcane.  The con for Nextcloud is that it feels heavy and is slow.

Nextcloud is a PITA to maintain via snaps in Ubuntu.  Something is always breaking or not working properly and most of those issues tend to be related to snaps.

I decided to try Nextcloud via containers.  I am very surprised - it feels light and quick in comparison to installing natively on HDD.  The host system has an SSD.  I deployed it via Portainer, but I had to butcher someone  else's docker compose YML file.  The file looks ugly but I've a running system.  This is my second attempt at deploying Nextcloud as a container - the first attempt had DB access issues that I was having a difficult time sorting.

Even when importing files (videos, pictures, and music) into Nextcloud, there was less of a system load.

For now, I'll monitor the system while using it with a small subset of data (it currently has 40 GB of files).  I don't want to spend the effort of moving a massive amount of files only for the instance to die (I do have persistent volumes enabled for the container, though).  The app container is consuming 4 GB of memory, though - that's a bit high, IMO...not sure if it's experiencing a memory leak, as it's using 4 GB while idle.

UPDATE (11/14/2025):

I decided to try to deploy a containerized Owncloud instance.  The compose YML file was a bit more beefy.  It was copied from the Owncloud documentation.  

I had to deploy this one from CLI, for now...I ran into an issue that I need to sort out - once I sort it out, I'll redeploy using Portainer.

I did run into an environment setting issue.  OWNCLOUD_TRUSTED_DOMAINS needed an IP value (IP of the server itself) - the documentation is vague on this and I found the answer from within a bug report.

I thought that a containerized Nextcloud instance was quick - this server is even quicker than a containerized Nextcloud instance.

I will have a bake-off of these two instances, but I suspect I'll be again adopting Owncloud as a docker cloud app.

UPDATE (11/17/2025):

One thing that is super weird is that Owncloud won't allow uploading of directories.  To upload a directory of MP3s, for example, I've to create a folder named, "MP3s" and then upload all the files within the MP3 directory.  WTF?!  

Note that I can move folders if I use the Owncloud client software.  I'm not wanting to install the client software on every system I have.  It's like they're actively fighting to not have a directory upload feature.  With Nextcloud (and Google Drive, and OneDrive), I just have to select the folder and the whole folder is treated as an object (meaning, the the directory and it's contents will be uploaded/downloaded).  It's damned silly not to include it.  

I think I ran into the same issue years ago when I used Owncloud (like 7+ years ago!).  I researched and someone said, well it works with Google...blame the browser creators (double-WTF?!)  Nah...I'm blaming Owncloud because things like that are silly and if they're doing things like this, what else are they doing within the code?  It looks like Owncloud decided for me which to use (and it's not Owncloud).  

I'm glad I didn't manually install it, only to see the lack of directory uploading.  

Ubuntu Desktop 22.04 and Dell XPS 8930

2-3 years ago, I bought my daughter a Dell XPS 8930.  It was nothing special but was a good base in case she needed to expand the system a bit.

Not long after purchase, the motherboard went bad.  I had on-site support for it but never got around to getting it repaired until maybe a month before support expired.  A contractor showed up and replaced the mainboard. 

My daughter only used it a few months then decided to build her own.  The XPS was sitting in a corner, barely used.

I've a cheap system I bought from TigerDirect that is running Ubuntu.  It is currently running Ubuntu Desktop 18.04.  I'd installed Owncloud on it, but the install got jacked up.  it's all out of sync now, package-wise.  I'd attempted to update Owncloud and it choked.  I've not been able to get it running again and it has crucial data on it (it has two drives and the Owncloud data is on the 2nd non-system drive).

I decide to run Ubuntu Desktop 22.04 on the XPS.  I'd initially installed LTS 22.04 but at this time that version has issues with systems that have Nvidia cards and I didn't want a headless system (I already have several of those), so I opted for Desktop.  The Desktop install was seamless.

Desktop 22.04 already has a cloud-based system included in the default install - Nextcloud.  I'm still playing with it but I'll more than likely use that since it's within the Ubuntu repository (Owncloud wasn't when I last checked).

Some things I don't like about these latest Ubuntu versions (noticed this will LTS as well):

• vim wasn't installed by default.  vi is installed by default.  I think this is a licensing thing (I don't believe vim is POSIX).  As well, if vi is already installed, I guess vim wouldn't need to be.  If anyone needs vim, they can use apt to install it post-install.
• ifconfig was not installed by default.  IMO, ifconfig should be essential to a default install.  You might need to troubleshoot a network issue immediately after installing the distro and if you don't have a network connection, you're screwed.  ifconfig is included in the net-tools package.  That package shouldn't be excluded from the base install.

Everything else seems to be good with this distro version, but I'm sure I'll find something amiss as I use the system.