The short answer is no. Rockstor is designed to manage docker integration itself.
The long answer is a bit more complex, but it largely comes down to “you’re playing with things that aren’t mean to be played with”, and as your modifications fall outside of supported configurations, I don’t foresee anybody knowing specifically how to resolve your issues.
In essence, if this were your 2004 Ford Escort, you’ve just come to ford asking why it stopped running when you put a 2019 Ford Explorer engine it. We don’t know.
The command you’re running, ‘ds’ has removed packages that Rockstor relies on, which means that the rockstor packages themselves have likely been removed as part of that - breaking your Rockstor installation.
In particular, part of your install script calls the following:
yum -y remove docker \
docker-engine > /dev/null 2>&1
This is removing docker, and everything that relies on it, and because of the
-y, it’s doing it forcibly, with no confirmation requests and no output.
This means that when the yum command wants to ask ‘In order to uninstall docker, I also need to remove rockstor-core and some other things’, it’s being told ‘yes’ in advance, and just does it.
As such, my first suggestion would be to try reinstalling the Rockstor base package from the repo, failing that - wipe and reinstall.
If you plan on doing things like plugin management (Rockons/Docker containers) manually, I strongly suggest that something designed as an appliance is not for you, and you’d be better off with a standard Linux install and configuring the OS to your requirements as you go.