Fix: export 'Interactive' was not found in 'remotion' (OpenShorts renderer)
Your first video free up to 60 minutes, then 20 free minutes a month, no credit card.
The fix: pin the render service to the same Remotion version as the compositions, then rebuild the renderer.
cd render-service
docker run --rm -v "$PWD:/w" -w /w node:18-bookworm-slim \
npm install --package-lock-only --save-exact \
@remotion/bundler@4.0.541 @remotion/renderer@4.0.541 remotion@4.0.541
cd ..
docker compose build renderer
docker compose up -d renderer
On Windows PowerShell, replace "$PWD:/w" with "${PWD}:/w" and put the command on one line.
Independent guide, not affiliated with OpenShorts. Checked on November 18, 2026 against mutonby/openshorts main and issues #116, #142 and #164, which were still open that day.
What the error looks like
After git clone and docker compose up --build, the backend and dashboard come up, but
openshorts-renderer keeps restarting. Its log ends like this:
[render-service] Initializing Remotion bundle...
[bundle] Bundling Remotion project from: /app/remotion/src/index.ts
[bundle] Progress: 100%
[render-service] Fatal error during startup: Error: export 'Interactive' (imported as 'Interactive')
was not found in 'remotion' (possible exports: AbsoluteFill, AnimatedImage, ...)
openshorts-renderer exited with code 1 (restarting)
Why it happens
The renderer image installs Remotion twice, from two lockfiles that have drifted apart:
| Lockfile | remotion | What it is for |
|---|---|---|
render-service/package-lock.json | 4.0.446 | The bundler and renderer that build the project |
remotion/package-lock.json | 4.0.541 | The caption and effect compositions |
Both package.json files ask for ^4.0.0, so nothing stops the drift. remotion/package.json
also needs @remotion/media ^4.0.447, and version 4.0.541 of that package imports Interactive from
remotion. The bundler resolves every remotion import to its own copy, 4.0.446, and that version does not
export Interactive. We checked both published packages: 4.0.446 has no Interactive export and 4.0.541 has one.
The fix, step by step
- Open the render service folder:
cd render-serviceinside youropenshortsfolder. - Rewrite its lockfile with Remotion 4.0.541, using the same Node 18 image the renderer is built on, so
npm ciin the image accepts it (the command is in the box above). - Rebuild only the renderer:
docker compose build renderer. - Start it and watch the log:
docker compose up -d renderer, thendocker logs -f openshorts-renderer. The bundle step should finish without the fatal error and the container should stay up.
This workaround comes from a reply on issue #116, whose author reported that a full upload, process and render job worked
after it. The longer-term fix suggested in the threads is to pin one exact Remotion version in both package.json files.
When upstream merges that, a plain git pull and docker compose up --build will do.
If it still fails
- "Missing: react@... from lock file" during the build: the lockfile was written by a different npm. Delete your edit with
git checkout render-service/package-lock.jsonand rerun the command insidenode:18-bookworm-slimas shown. - A Node version warning about
@rspack/core: issue #142 reports that warning on Node 18. Bundling and rendering still worked in that test. - Something else: read issue #142, which has the full analysis, and the OpenShorts install guide.
Would rather not run Docker at all? AIClipMaker.org is a hosted build of the same engine, and your first video is free.
FAQ
- Why does the renderer say 'Interactive' was not found in 'remotion'?
- The image installs two Remotion versions. render-service/package-lock.json pins remotion 4.0.446, while remotion/package-lock.json installs @remotion/media 4.0.541, which imports Interactive. Remotion 4.0.446 does not export it, so the bundle step fails and the container restarts.
- Is my install broken, or is it the repository?
- The repository. A fresh clone of main hits it on every platform. Nothing you configured causes it.
- Does docker compose build --no-cache fix it?
- No. The versions come from the committed lockfiles, so a clean rebuild installs the same two versions again.
- Why run npm inside a node:18 container instead of on my machine?
- The renderer image builds with Node 18 and runs npm ci. A lockfile written by a newer npm on your machine can fail npm ci in the image with a 'Missing: ... from lock file' error, as reported in issue #116.
- Do I need the renderer for basic clipping?
- The backend starts and answers its health checks without it, but the renderer is the service that draws the animated captions, hooks and effects, so jobs that use them need it running.