Since that post is locked I am asking here:
VMWARE Installation is now only available for the community edition?
Also, how is the plan? What is the deadline when VMARE installs are no longer support?
I just want to make sure, we are ready to migrate to a Docker version before that time.
Just to tag on the back of this. Are you saying it’s just future vmware installs? I am hopefully assuming that current vmware installs will be supported for upgrades etc?
Well, that escalated quickly. All my instances are sauce code installs….
On the VMware front, my understanding it’s it’s basically docker on VMware, so I suspect it’s no big deal, unless it’s old enough to be a sauce code on VMware install (docker joined the chat about 3 years ago I’m remembering correctly).
To throw some light here, for some years now, the Eramba installation method is by using Docker (the Docker installation method was released in August 2022). The VMware installation you see on the learning portal also uses Docker; it’s Ubuntu 24, with Docker and the Eramba Docker image downloaded.
That versions, both Docker and VMware (still Docker) are supported and will continue to be available for both enterprise and community.
The version that is starting EOL is the source code installation (the version that was installed directly on the OS), regardless of whether it’s on your own server or VMware.
The EOL is on 3.30 version, so our recommendation will be to migrate to docker while on 3.29
VMware installs are supported as long as Eramba runs on Docker!
If your install is before Q4 2022, then there is a good chance that it is a source code install; those source code installs are the ones that will get end of life.
So you say source code installs are going EOL, but are updates still being supported for original source code installs?
Updates for source code will also be EOL. The latest supported version for source code will be 3.29.1. After that, you will need to migrate to Docker in order to update to 3.30+.
We have been using Eramba for so long, the VMWARE install we have is actually a source code install, no Docker in that image.
Is there a dedicated migration plan available or is it as simple as doing a File Backup and a Database Backup from within Eramba and then import them in a new Docker-based setup?
Same as our setup. This seems to have come out of the blue tbh and we will need to do a lot of planning for this, so detailed migration steps would be great.
It’s simply exporting backups from source code and importing them on a Docker-based install running the same version number.
To make things clear, we’ve created a dedicated guide:
https://discussions.eramba.org/t/guide-migrating-source-code-install-to-docker-install/8487/3
