Multiple instances on the same machine data collision. Modify used paths

Meeting SDK
1

Meeting SDK Type and Version

6.7.5 Linux

Description
Meeting SDK creates and uses folders on system like /var/.zoomsdk and /var/opt/zoomsdk. It is ok when I run single instance but when two at the same time, or when app is restarted I see SQL errors.

Questions:

  1. How can I run multiple Meeting SDKs on the same machine?
  2. How can I modify folder paths that Meeting SDK uses?

Error
zoom-bot-sample | 2026-03-04 10:08:33.977: ERROR CORE sqlcipher_page_cipher: hmac check failed for pgno=1
zoom-bot-sample | 2026-03-04 10:08:33.977: ERROR CORE sqlite3Codec: error decrypting page 1 data: 1
zoom-bot-sample | 2026-03-04 10:08:33.977: ERROR CORE sqlcipher_codec_ctx_set_error 1
zoom-bot-sample | 2026-03-04 10:08:33.978: ERROR CORE sqlite3Codec: identified deferred error condition: 0

How To Reproduce
1. Launch 1st instance of app that uses Meeting SDK
2. Launch 2nd instance of app that uses Meeting SDK
3. Check logs

2

Zoom’s Meeting SDK isn’t designed for multiple concurrent “instances” sharing the same machine state: it even defines SDKERR_OTHER_SDK_INSTANCE_RUNNING, and Zoom staff have called multi-instance workarounds (like sdkPathPostfix) unsupportedand subject to breaking on upgrades.

For something you can rely on, you’ll need to isolate each bot in its own container/VM (or separate host) so the SDK’s local files don’t collide.

You could also consider using a Meeting Bot API or Desktop Recording SDK from Recall.ai, depending on whether you want bot-join or on-device capture.

3

@pavlon since you are running Linux SDK, you would want to run them each in their own docker container for this scenario.

4

@chunsiong.zoom @amanda-recallai thanks for your answers!

What worked for me is setting different HOME env variable for each instance. No more errors like that.
Checked 2 meetings in parallel and it worked.