@WD_Admin are you prepared to look at the above?
Loss of Docker is a BIG deal for many people.
@WD_Admin are you prepared to look at the above?
This is a MASSIVE loss. WD are nuts to do this. Many folks have leveraged the docker instance to make the NAS incredibly. Powerful. Zero chance I’ll be upgrading until this is restored.
Just installed the 5.04.114 release onto my EX4100 and suprise, suprise, docker still does not work and still does not look like it has the MQUEUE kernel support compiled in. WD asked us for feedback, and it looks like the feedback was ignored.
Why bother ?
This morning I received the email stating My Cloud had a new version. I was happy and ready to install, yet I saw a small note indicating I must reinstall all my applications, so I did a quick check if all my applications where supported… I use docker very much, home assistant, esphome, pihole, mosquito, portainer… All my smart home system works with containers under docker. If I had installed the new my cloud 5 I would have lost my complete smart home functionality, I would be very very pissed.
I think that up front WD should put a big note stating the applications that doesn’t work under my cloud 5, docker should be the first one listed.
I will not update to My Cloud 5 until docker is 100% supported and bug free.
Well. . . from what I have seen, the “beta” program was focused on bug fixes. . . . not feature issues.
From what I have seen in the beta program; I will bet that there was a “functional spec” written for OS/5 - - - probably based upon a glossy powerpoint presentation - - -and that functional spec does not appear to have been open for discussion with the user base.
Probably because changing functionality in the beta test would have blown up the timeline (and software budget) for this release. I would not underestimate the need for, and the amount of, under the hood changes required to improve security and develop the new Web/app interface.
Unfortunately, most of the feedback has actually been related to functionality. . . .
. . . .and this will likely be the focus of the user judgement on the software.
Ok, this is just annoying now, and WD would do well to provide some additional guidance to the community here. Docker on the PR2100/PR4100 works just fine for me (YMMV).
It does, however, require the install of an “app” to enable it. The app can be found here: https://github.com/WDCommunity/wdpksrc/issues/57 (specifically at this link: https://github.com/WDCommunity/wdpksrc/files/5152595/docker-19.03.8-OS5.zip)
It appears the specifics of this thread are primarily related to the EX4100 device which apparently no longer supports Docker.
Yessss!!! Seems to be working for me too (PR4100). Hooray!!! That’s SUCH good news.
Agree with you 100% on your comments, however in the old OS3 release, the kernel was compiled with MQUEUE support and I believe the default is to compile it into the kernel, so this means that WD made the conscience decision to not include it in the kernel explicitly.
Looks like they have used different compile options for the kernel on the PRX100 series compared to the EX4100.
@Tfl has done some great work preparing a number of packages for use with OS5.
Thank you so very much. I updated to OS5 today, and I couldn’t get the old docker .bin to install. My heart dropped into my stomach.
Yes, we should all be sending him/her/them ale vouchers (aka cold hard cash)
I have a PR2100 I try MyCloudPR2100_docker_19.03.8 it installs fine with no issues but when trying to login to Portainer I get this error " Failure Unable to retrieve endpoints " I did upgrade to My Cloud OS 5
on EX2 Ultra it installs fine, even “dockerd” daemon is running, but containers cannot be run since “MQUEUE” capability is missing. What a shame. I really want to downgrade to OS3 now
Looks like WD are looking into the issues with Docker seriously :
Docker : While Docker was not officially supported in My Cloud OS 3, we understand this is important for you. We are looking into a way to configure our Linux Kernel configuration so Docker can be manually added. This task may take some time, and we will let you know as soon as we have an update.
Full post @ Update on My Cloud OS 5 feedbacks
Docker was originally supported on the OS3 platform and was the chosen way to deploy new applications until they made the current packaging platform available for OS3, but who is picking straws here.
v5.06.115 announced compatibility with Docker as it added POSIX_MQUEUE and SECCOP support to kernel for EX2 Ultra.
But it seems the OS5 Docker package still does not work correctly on EX2 Ultra.
More details in thread here.
Replied to this on the other thread indicating steps that you can do to get it working.
WD announced they will be releasing firmware to reintroduce docker support and are working on it right now.
They also released yet another firmware update (what’s that, 3 in 2 weeks?) fixing some security bugs they introduced with the auth system, and also announced they are going to provide an alternative solution to the auth redirect that everyone hates. Oh and 3 of my apps had security updates too, lol.
There’s some SERIOUS amount of backpedalling on the WD bicycle this week. Turns out when your community explodes with several hundred threads thrashing your mongoloid release you say sorry and crawl back into your server room.
Would you rather they did not try and make an effort to fix the issues that people are raising ? I think it is a good thing and they are making progress with each release.
In saying that, a better strategy would have been to avoid all of this by making sure these features they are now re-adding were in the original OS5 release to start with and avoid a lot of grievances from the users of their product.
Oh for sure I’m in favour of them updating frequently and providing fixes for these issues. Likewise I agree with you about how they should have avoided this whole mess by not removing most of these features in the first place.
This has to be one of the worst product roll outs in recent times. Taking away so many features, introducing ones that people didn’t ask for, having their community team spend two weeks defending the changes and stating that the removed features are no longer supported, it’s just a total mess. Whatever product manager or team that was put in place to coordinate and deploy this release really made a mess of it.
I’m happy that they are sorting it out though, but I know it’s only because all hell broke loose, rather than out of their understanding of the users or customers. They spent so long telling us that these features and changes were the new norm and basically releasing PR responses without properly addressing our concerns that it’s clear that they actually did not comprehend their mistakes or actually care about the consequences of their decisions.
Maybe now all this blowing up in their face spectacularly will make them reconsider future development decisions, but I wouldn’t hold my breath about this. Remember, this is the company that released drives with SMR on them without declaring it and are currently losing a lawsuit because of it. I don’t trust them to not be despicable anymore.
I would argue that these grievances affect a very small portion of the user base. Those of us who have gone in and used Docker or used other mods on our devices to push their limits happen to be the most vocal. I don’t disagree with it being frustrating and wildly inconvenient. Having been part of the beta, it was obvious that there definitely are users asking for certain features they implemented. All that to say, we don’t represent a single monolith of WD NAS users.