Upgrade (container)
Warning
Before performing any upgrade, ensure a complete backup exists of all container-mapped configuration and data directories.
Container v7.2026.1
This document describes how to upgrade an elDoc container deployment from any 5.x version to container v7.2026.1.
Prerequisite: Stop the running elDoc container with version 5.x before continuing.
1. Upgrade MongoDB Feature Compatibility Version
Before upgrading the container image itself, you should update the MongoDB Feature Compatibility Version (FCV) to match the newer binaries included in elDoc-AIO Container v7.2026.1.
Note
A MongoDB root user password is required. By default, on the initial container start, the root password is stored in:/opt/eldoc/conf/mongod/root.properties
elDoc v7.2026.1 includes MongoDB 8.2 binaries. It is strongly recommended to upgrade your MongoDB FCV from 7.0 to 8.2 prior to starting the updated container.
1.1. Upgrade FCV: v7.0 → v8.0
1. Determine the ownership (UID and GID) of the existing MongoDB data and config directories::
# ls -aln /opt/eldoc/conf/mongod && ls -aln /opt/eldoc/data/mongoData total 12 drwxr-xr-x 2 0 0 66 Feb 4 17:29 . drwxr-xr-x 6 0 0 57 Feb 4 17:29 .. -rw-r--r-- 1 0 0 356 Feb 4 17:29 mongod.conf -r-------- 1 994 994 1024 Feb 4 17:29 mongod.key -rw-r--r-- 1 0 0 39 Feb 4 17:29 root.properties total 6388 drwxr-xr-x 5 994 994 20480 Feb 4 20:45 . drwxr-xr-x 4 0 0 39 Feb 4 20:34 .. -rw------- 1 994 994 36864 Feb 4 20:45 collection-0-1288614533251612643.wt -rw------- 1 994 994 32768 Feb 4 20:45 collection-0--2985901231547264096.wt -rw------- 1 994 994 4096 Feb 4 17:48 collection-0--3575194380845372456.wt
2. Launch a temporary MongoDB 8.0 container using the same UID/GID and bind mounts for the data and config:
podman run --rm --name mongodb --user 994:994 \ -v /opt/eldoc/conf/mongod:/local/conf/mongod:Z \ -v /opt/eldoc/data/mongoData:/local/data/mongoData:Z \ -v /opt/eldoc/logs/mongod:/local/logs/mongod:Z \ docker.io/library/mongo:8.0 \ mongod \ --dbpath /local/data/mongoData \ --keyFile /local/conf/mongod/mongod.key \ --auth \ --replSet rs0
3. From another terminal, exec into the running container and open the MongoDB shell:
# podman exec -it mongodb /bin/bash # mongosh -u root --authenticationDatabase admin
4. In the MongoDB shell, check and update the Feature Compatibility Version. Confirm the update was successful (it must be similar to the examples provided below):
$ db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
{
featureCompatibilityVersion: { version: '7.0' },
ok: 1,
'$clusterTime': {
clusterTime: Timestamp({ t: 1770230043, i: 1 }),
signature: {
hash: Binary.createFromBase64('FrTPI2NbujnGW/LcUNr8943rx4M=', 0),
keyId: Long('7603048169345122311')
}
},
operationTime: Timestamp({ t: 1770230043, i: 1 })
}
$ db.adminCommand( { setFeatureCompatibilityVersion: "8.0", confirm: true} )
{
ok: 1,
'$clusterTime': {
clusterTime: Timestamp({ t: 1770230065, i: 2 }),
signature: {
hash: Binary.createFromBase64('R3t/N7rEfQrhr90/FDwayLaRXlc=', 0),
keyId: Long('7603048169345122311')
}
},
operationTime: Timestamp({ t: 1770230065, i: 2 })
}
$ db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
{
featureCompatibilityVersion: { version: '8.0' },
ok: 1,
'$clusterTime': {
clusterTime: Timestamp({ t: 1770230065, i: 2 }),
signature: {
hash: Binary.createFromBase64('R3t/N7rEfQrhr90/FDwayLaRXlc=', 0),
keyId: Long('7603048169345122311')
}
},
operationTime: Timestamp({ t: 1770230065, i: 2 })
}
5. Confirm the update was successful, then exit and stop the temporary container.
1.2. Upgrade FCV: v8.0 → v8.2
1. Start a temporary MongoDB 8.2 container in the same manner:
podman run --rm --name mongodb --user 994:994 \ -v /opt/eldoc/conf/mongod:/local/conf/mongod:Z \ -v /opt/eldoc/data/mongoData:/local/data/mongoData:Z \ -v /opt/eldoc/logs/mongod:/local/logs/mongod:Z \ docker.io/library/mongo:8.2 \ mongod \ --dbpath /local/data/mongoData \ --keyFile /local/conf/mongod/mongod.key \ --auth \ --replSet rs0
2. From another terminal, exec into the running container and open the MongoDB shell:
# podman exec -it mongodb /bin/bash # mongosh -u root --authenticationDatabase admin
3. Update the FCV to 8.2:
$ db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
{
featureCompatibilityVersion: { version: '8.0' },
ok: 1,
'$clusterTime': {
clusterTime: Timestamp({ t: 1770230362, i: 1 }),
signature: {
hash: Binary.createFromBase64('wG3l8lRwlhIGgQK6XguEr9mo+0s=', 0),
keyId: Long('7603048169345122311')
}
},
operationTime: Timestamp({ t: 1770230362, i: 1 })
}
$ db.adminCommand( { setFeatureCompatibilityVersion: "8.2", confirm: true} )
{
ok: 1,
'$clusterTime': {
clusterTime: Timestamp({ t: 1770230381, i: 43 }),
signature: {
hash: Binary.createFromBase64('LiTndvSmteAgXmsO0IcaUufSj8A=', 0),
keyId: Long('7603048169345122311')
}
},
operationTime: Timestamp({ t: 1770230381, i: 43 })
}
$ db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
{
featureCompatibilityVersion: { version: '8.2' },
ok: 1,
'$clusterTime': {
clusterTime: Timestamp({ t: 1770230402, i: 1 }),
signature: {
hash: Binary.createFromBase64('JXX3hyKqWd0mjCmp+Cn5xk8rXEM=', 0),
keyId: Long('7603048169345122311')
}
},
operationTime: Timestamp({ t: 1770230402, i: 1 })
}
4. Confirm the update and stop the temporary container.
Once completed, your stored MongoDB data will be compatible with the upgraded container version.
2. Update JMC Configuration
1. Open the config-eldoc.json file located under: /opt/eldoc/conf/jmc
2. Find the line: "docManager": "ua.eldoc.jmc.docman.ElDocSolrDocManager"
3. Replace it with: "docManager": "ai.eldoc.jmc.docman.ElDocSolrDocManager"
This change ensures the correct document manager class is used by the newer elDoc runtime.
3. Restart the Upgraded Container Image
After completing the MongoDB and JMC configuration updates:
Pull or reference the updated elDoc container for v7.2026.1:
podman pull registry.eldoc.online/eldoc/eldoc-aio:latestorpodman pull registry.eldoc.online/eldoc/eldoc-aio:7.2026.1Start the new container with your existing volume mappings and environment variables.
The new elDoc container will now run with updated dependencies and MongoDB compatibility.
Last modified: February 08, 2026