[RESOLVED] Rockons in openSUSE

I’m attempting to get Crashplan PRO working on an openSUSE installation. I recently migrated from CentOS and I pulled the JSON I was using from the flash drive so I’m reasonably certain that it is correct. Is running a custom Rock-On the same in openSUSE as it was in CentOS?

/opt/rockstor did not contain a rockons-metastore subdirectory. I created it, placed my json there, and hit refresh on the Rock-Ons/All page. The Crashplan Pro Rock-On did not show up. I then cycled the Rock-On service off and back on, and still no Crashplan Pro.

Path, filename, and file contents are shown below.

➜ rockons-metastor pwd
➜ rockons-metastor ls -alh
total 4.0K
drwxr-xr-x 1 root root 34 Dec 29 06:58 .
drwxr-xr-x 1 root root 394 Dec 29 06:57 …
-rw-r–r-- 1 root root 981 Dec 29 06:58 crashplanpro.json
➜ rockons-metastor cat crashplanpro.json

  "Crashplan-Pro": {
    "containers": {
      "crashplan-pro": {
        "image": "jlesage/crashplan-pro",
        "launch_order": 1,
        "ports": {
          "5800": {
            "description": "WebUI port.",
            "host_default": 5800,
            "label": "WebUI port",
            "ui": true
          "5900": {
            "description": "VNC port.",
            "host_default": 5900,
            "label": "VNC port"
        "volumes": {
          "/config": {
            "description": "Choose a share for the crashplan configuration & log files.",
            "label": "/config"
        "opts": [
    "description": "Crashplan Pro rockon, container from jlesage/crashplan-pro",
    "website": "https://hub.docker.com/r/jlesage/crashplan-pro/",
    "volume_add_support": true,
    "version": "beta"

Hello @Noggin, hope all is well on your side,

Yes, it is the same. I have not looked at your rock-on json in details yet, but there is one thing that could explain why you the new rock-in is not showing up in your list: Could you verify your path? Indeed, it appears you are using the following path in your system…


…whereas it should be:


Note the missing “e” at the end of “metastor” in your example. It could thus be as simple as a little typo in your path.


That’d be it! I’m gonna blame this one on the developers. This would have been a good time for a meta-joke… Rockstor… metastor…

OK, fine, PEBCAK. It’s always PEBCAK. Unless it’s not, and even then it’s probably still PEBCAK.

Thanks Flox!