PSA: Don't simply update container image in Docker just because it is easy to do. It's so easy to just click 1 time on the update to update it. Read the developer or maintainer release note first.

I updated my Jellyfin server container without reading it first and after update the container stopped immediately after run. Then only I read release note and found out need to stop the container first before update. Also need to update to v10.10.7 before update to the latest v10.11.0, unfortunately I was on v10.9 when I update and run the container. Going from v10.9 directly to v10.11.0 causes the database or config files to be corrupted. I re create back v10.9 container but the server still can't run because the database or config files have corrupted. All the weeks spent to set up the database for the image, description, grouping and many more now all gone.

Never guessed that I have luck on my side. Turned out I have set Snapshot Replication to run every 2 hours for Docker config & cache folder. I restore back the snapshot before update to v10.11.0, re create v10.9 image and it run as if nothing has happened before this.

Another PSA: make sure to have snapshot or versioning for all your files. This is like rewind function back to before the mess up.

the problem with auto updating docker container images to update the app are a couple of things

Cons

1. it MAY or MAY not break your docker container for that app. It may come as a surprise to some, but some of these updates entail ALSO editing your YAML file as WELL as updating the image. Just updating the image might not be sufficient. This is why you have to read the changelog to see if any of those edits need to be done or not. It doesn't happen frequently, but it does happen. An example is Immich. Few times i noticed that broke because didn't update the YAML docker compose file for the new changes.

2. Some of these docker repositories do get hacked into from time to time. The most serious recent case was one repo used by the popular nginx proxy manager. So those malware got onto NPM, and people who simply auto update got a surprise malware that they themselves had auto updated to their NAS.

https://www.bleepingcomputer.com/news/secur...7-npm-packages/



Pro

1. just the usual keep it up to date

2. too lazy to check for update, so you use something like watch towerr to check for new image, then to update based on your own set schedule, daily, weekly? monthly?




For the 1st con that breaks docker containers, one way to deal with that is only set auto update for NON CRITICAL docker container apps. So even if it does break it's not a big deal.


But even then, this does not solve the 2nd problem which is rather serious. You are fully entrusting your NAS security to the github developer.

Well as you can see even they get lax on security and got hit by phishing attacks, and the supply chain they used those resources without any sort of checks, thinking it was safe (it wasnt), then everyone who also trusted npm got hit.

So one method you could do for a balance between auto updating and security safety, don't set the auto update to daily. Set it to like weekly or monthly. Why? because when you stagger an update this way, it gives you time for the github devs to discover and remove these infected packages.

But this is assuming that it does get discovered in the nick of time. Some malware often go undetected for long periods. So it's not a full proof method but it's something.


For backing up your docker container apps, at least in truenas, i suggest you set a fixed location for where you store

1. your yaml docker config templates. For dockge they do this.

2. save a fixed location where your docker data is stored.


Next, STOP all the docker containers from running. I'd go to dockge and stop them. Once done, then run your backup. I use the truenas rsync in the data protection section in UI. This backups the docker templates and data to my backup NAS.



another thing to be aware of, you think that just because you update means that all the security issues got patched, yes? that is not always the case. Often the docker image comes bundled with stuff that has many vulnerabilities that to date haven't been patched. This is why some packages these days have become more popular because they use a leaner setup thus reducing the stuff that may contain vulnerabilities.

Linux alpine builds for example






If you are wondering whether a docker container image has vulnerabilities, you can use something like Trivy to check




then you would at least be somewhat informed that the image you want to deploy has this vulnerability and whether you think its worth using or not.

If it's low risk should be ok. if it's critical, definitely not



Some docker container projects receive so much flak for their lack of security patches that they end up in the news
https://www.securityweek.com/dozens-of-squi...ter-disclosure/


like this squid proxy which you should NEVER use any docker container images with a similar issue most often some docker container images are no longer maintained, or they are lax on vulnerability patches, one it reaches that point, i recommend you find alternatives and don't use that docker image anymore.

if you are unsure as the project is merely 1-2 year not maintained, you can run a trivy scan and check how many vulnerabilities it accrued and remained unfixed but the rule of thumb, if updates is 1-2 year no activity, it's time to move on.

This post has been edited by Moogle Stiltzkin: Nov 2 2025, 07:59 AM

With the ssd and ram price getting out of hand and I need more storage now. After some checking all the external hdd are now smr drives, many of the ext. hdd price are more expensive than a proper nas drive. If look at the dash solution, most of the das enclosure are using shitty controllers. I'm thinking maybe it's time to invest in a proper nas. Since I'm planning to use it for >5years.

Currently looking at:
1. Ugreen NASync DXP4800/Plus 4-bay
2. Ugreen NASync DXP2800 2-bay

NAS Drives:
1. Seagate IronWolf 4G < Cheapest
2. WD Red Plus 4G < About 100-200+ pricier than IronWolf
3. Toshiba N300 4G < Most expensive double the price

Still debating either bite the bullet go for 4 bay for future storage expansion or 2-bay no future proof for storage expansion. hmm...

My suggestion is to go for 4 bays. You could use 2 bays for now and still have another 2 bays for future needs. Now you haven't use NAS yet so you won't see what else can be use for it. When you start using it then you'll have more ideas for it's usage and the storage needs will also be more.

Hi bro. Last month, I just bought DXP4800Plus (4-bay) & 2x10TB Seagate IronWolf Pro. My first NAS build. Set at RAID-5.

Not a power user. I have an old PC (2012 spec) that have files/life photos/medias since 1997 until 2023 that I plan to keep and build proper archive. Also, some work files many in 2.5inch HDD scattered around the house, gonna trim Google Drive subscriptions and also use the NAS for home media streaming movies/FLAC audio files. Gonna dispose the old PCs, old external HDDs, so less clutter in the house. Now I only use laptops and centralize every storage needs on the NAS.

The DXP4800Plus has better spec than DXP2800 apart from extra two HDD bays, better processor, expansion slots for RAM and SSD.

The current setup costs me around 5.5k but I think it's worth the investment in the long run. Gonna get additional 2x10TB when the time comes, though I think not in the near future.

p/s - I was almost getting Synology DS925+ but found out the DXP4800Plus has better spec and not to mention the HDD brand scandal (though recently lifted I heard).

Yea, I plan to slowly upgrade the ram and ssd, since the price are now sky rocketed
After evaluating 2bays and 4bays I think I will go with 4 bays since I can do more with it, docker, vms etc, like building up tiny little home lab.
For HDD I think I might bite the bullet get 4pcs 4TB each and run raid5, will see the price to9 and decide later.

Yo bro, your situation is kinda similar like me.
How much you are getting for the DXP4800Plus alone? From Laz or Shopee?
I think I will go with DXP4800Plus and get 4x4TB IronWolf (Non-pro) since it's the cheapest nas drive out there. each est RM470++.

Yes the reason I'm getting a nas is because I'm currently "building" up a digital time bomb.
My current setup:
- 3 separated 500gb old ext. HDDs from year 2009-2013 (gotta phase out all of it)
- 1 2TB WD passport from year 2019
- 1TB samsung T7 year 2023
- 2TB samsung T9 year 2025
- Desktop PC
- Macbook

I've lost TBs of data couple of years ago when 2 of my ext hdds dies.
If i want the cheapest way to do it, I could have just bought 2x4TB ext HDDs and call it a day.
After some calculation, getting 2 seagate one touch 2tb already cost around RM1k and it's using SMR drives.
Or get the Seagate desktop hub 8TB, cost around RM1.xk++, it's using single barraCuda drive, so it's not a backup solution. The Seagate LaCie d2 or 2big RAID 8TB is crazy expensive and it's just a DAS.
So after evaluating I think is just not feasible continue to use ext. hdd.
Yes the upfront cost is high, but in the long run I think is better to pay for any cloud storage.

10TB n above need special cooling solution de.. u hv tat??

Similar situation!

RM2799 for the DXP4800Plus at Asashi. Online is cheaper but I prefer this Asashi branch because it is near my home, in case of need to RMA etc. Don't really have time to do postage/returns on my own, these days.

I remember ugreen official shopee mall was selling RM2450 (inc. shipping) at that time.

10TB below HDD can just use without a fan, ie passively cooled? and 10TB and above HDD MUST have fan?

ambient temperature need below 16C... air con a must.. helium will leak very fast under room temperature

Synology Drive 4 before this under Beta, now it is released as stable. Now can do file locking and file request. Also optimized file monitoring

Added support for shared labels, allowing users to organize, search, and manage files and folders collaboratively.

Added support for creating file requests, making it easy for users to collect files from external parties without requiring them to sign in.

Added support for file locking to prevent conflicts from concurrent edits through manual or automatic locking.

Optimized file monitoring to reduce conflicts with resource-intensive applications, improving Synology Drive stability under heavy workloads.

Added support for enabling tiered shared folders as Team Folders. Note: This feature is not supported by Synology Drive ShareSync. If a Team Folder is included in a tiering plan, you cannot create a sync task based on this folder in Synology Drive ShareSync.


Synology Drive Web Portal

Added the "Manage Team Folder" feature, allowing admins to enable or create shared folders as Team Folders directly on the web portal.

Added a "Deleted Time" column in the Recycle Bin to help identify recently deleted files.

Added support for previewing WebP and JFIF image formats.

https://www.techpowerup.com/343867/penguin-...400-ecc-csodimm

Bro got some RAMs you can hit me up for cheaps?

yikes, never know about that... luckily my toshiba mg06 10TB are not helium filled, been running 3years average temperature around 40-45c