Failed to install dependencies

Need help
1

Hello, I installed Active Pieces on my NAS with Docker and recently performed the latest update, and since then I have been experiencing an issue.

Active Pieces no longer responds to any commands whatsoever (I can go into the menus and navigate, but when I try to publish or enable/disable, it does not work) and in the logs I have this:

2025-12-08T12:48:00.725334715Z 2025/12/08 01:48PM 30 | pid=10 hostname=b976c7549bf4 path=/usr/src/app/cache/v7/codes timeTaken=0ms msg=Installed code in sandbox 

2025-12-08T12:48:00.725372595Z 2025/12/08 01:48PM 30 | pid=10 hostname=b976c7549bf4 path=/usr/src/app/cache/v7/common timeTaken=0ms cacheHit=true msg=Installed engine in sandbox 

2025-12-08T12:48:00.725382354Z 2025/12/08 01:48PM 30 | pid=10 hostname=b976c7549bf4 rootWorkspace=/usr/src/app/cache/v7/common piecesToInstall=["@activepieces/piece-schedule-0.1.13"] msg=[registryPieceManager] Installing pieces in workspace 

2025-12-08T12:48:00.725389491Z 2025/12/08 01:48PM 30 | pid=10 hostname=b976c7549bf4 rootWorkspace=/usr/src/app/cache/v7/common pieces=["@activepieces/piece-schedule-0.1.13"] msg=[registryPieceManager] acquired lock and starting to install pieces 

2025-12-08T12:48:00.725396555Z 2025/12/08 01:48PM 50 | pid=10 hostname=b976c7549bf4 error={} msg=[PackageManager#install] Failed to install dependencies 

2025-12-08T12:48:00.725402767Z 2025/12/08 01:48PM 50 | pid=10 hostname=b976c7549bf4 rootWorkspace=/usr/src/app/cache/v7/common pieces=["@activepieces/piece-schedule-0.1.13"] error={} msg=[registryPieceManager] Piece installation failed, rolling back
2

I experience similar problems with latest version/s. I can navigate into flows but any action i try to test doesn’t work. It just loads and waits for long time until I get a message “internal error, contact support”. It affect all pieces I try to test in the flow, built in ones (get current date) and other connections I added.
In have opened a GitHub topic about it in issues but only got a bot reply to a link in “linear”.

I have rolled back to 0.70 for now.

1 Like
3

Hi @igalg2024 and @Zakarik,

We recently switched to Bun, and it seems Bun doesn’t support older CPUs. They have a specific build for these CPUs. We tested it, and the original issue was resolved, but another issue appeared.

We’re looking into a solution.

Thanks,
Mo.

1 Like
4

Thanks 0.70 works for me at the moment.

5

Any news about this?

6

Hi guys, also looking forward to the fix. Reverted to 0.70 for now.
Works on Synology DS442+.