Docker Engine can't install or enable

[ATOMFIX]

I recently had to reinstall TOS because i broke the NGINX file for the TOS dashboard. All is working again now but I can't get Docker Engine working. It only shows the enable button. But comes up with operation failed. Can't uninstall. and SOMETIMES, it might just show the install button again, when clicking install, it's sometimes instantaneous or it will show another error saying my TOS is out of date and to update.

F6-424 Latest TOS OS

[TMeric]

Could you please specify the version of your TOS? Our latest system version is 6.0.783, and we have verified that Docker Engine can be properly disabled or enabled.
You may try uninstalling and reinstalling Docker Engine, and also check if the NAS time settings are correct.

[ATOMFIX]

Apologies for the delay. Latest TOS version out available. I've reinstalled at least 5 times now. Docker Engine keeps disabling itself

[ATOMFIX]

Docker Engine Version: 27.2.1 and TOS: 6.0.783.01200

F6-424. Correct Time and Date used. I've tried uninstalling and reinstalling Docker engine numerous of times, even reinstalling TOS several times. Docker Engine doesn't work, sometimes I get a error saying TOS Version is not compatible but most of the time it's operation failed

[ATOMFIX]

I have previous Docker Engine install on /Volume3/ But I cant uninstall. Even though in App Settings app install set to /Volume1/ it keeps breaking.

Using SSH I found found a lot of docker engine related files on /Volume3/ but I can't remove them as sudo is disabled in SSH

name@TNAS:~# btrfs device stats /Volume3
btrfs scrub status /Volume3
[/dev/mapper/vg2-lv2].write_io_errs 0
[/dev/mapper/vg2-lv2].read_io_errs 0
[/dev/mapper/vg2-lv2].flush_io_errs 0
[/dev/mapper/vg2-lv2].corruption_errs 1190
[/dev/mapper/vg2-lv2].generation_errs 0

BTRFS has locked into read-only mode because of the corruption errors which I need to delete

[CursaYang]

When using the terminal in TOS 6, the default is to use the super administrator user, which has the highest privileges and does not require the use of sudo again. Based on your description, there may be Btrfs file system errors. It is recommended to check and repair them.

[ATOMFIX]

Apologies for the late reply. BTRFS locked down the file system to read-only. Why it got corrupted who knows.... but the errors were unrecoverable. So I had to wipe the volume in the end.