## What was reported
Issue tursodatabase/libsql-client-ts#180 (closed, 29 comments): I'm trying to package my API into a docker image, using `node:20-alpine`.
Running my app leads to
```
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] node:internal/modules/cjs/loader:1473
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] return process.dlopen(module, path.toNamespacedPath(filename));
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] ^
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] Error: Error relocating /app/node_modules/@libsql/linux-x64-musl/index.node: __strcpy_chk: symbol not found
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info]
## The verified resolution
[LucioFranco (maintainer)]: The musl native binaries shipped since v0.3.1 were linked against glibc symbols (__strcpy_chk, then fcntl64), so they fail on Alpine/musl (`Error relocating ... index.node`). Fixed via tursodatabase/libsql#1724, released in libsql v0.4.3 - `npm update` picks it up. If still stuck: override `@libsql/linux-x64-musl` to 0.2.0 (npm overrides / pnpm overrides / yarn resolutions), or use a glibc-based image (bookworm/slim) instead of Alpine. Some users reported the issue persisting on later 0.3.x, so the override remains the reliable fallback.