Error executing tailwindcss-linux-64 in a Docker container.

[dmarczal]

When I try to execute any command with tailwindcss-linux-64, I get the following error:

$ ./tailwindcss-linux-x64 
22676 |     };
22677 |   };
22678 | });
22679 | 
22680 | // ../../node_modules/.pnpm/@parcel+watcher-linux-x64-glibc@2.5.1/node_modules/@parcel/watcher-linux-x64-glibc/watcher.node
22681 |   module.exports = __require("/$bunfs/root/watcher-0pmc4yjg.node");
                                    ^
error: /tmp/.5ef7debfbdfbdf59-00000000.node: failed to map segment from shared object
 code: "ERR_DLOPEN_FAILED"

      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:22681:29)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:18:47)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:22697:42)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:18:47)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:64070:44)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:28:48)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:64154:13)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:28:48)
      at <anonymous> (/$bunfs/root/tailwindcss-linux-x64:64276:46)

Bun v1.2.4 (Linux x64 baseline

Version 3 works normally, but in version 4, this error occurs.

Any suggestions? May I need a specific dependency in the container?

[nathancolgate]

FWIW: We had this same problem running inside a docker image based on a ruby slim bullseye image. Based on the guidance here:

https://github.com/flavorjones/tailwindcss-ruby#using-a-local-installation-of-tailwindcss

We used our package installer to add the following to node_modules:

    "@tailwindcss/cli": "^4.1.8",
    "tailwindcss": "^4.1.8"

And then in our Dockerfile:

ENV TAILWINDCSS_INSTALL_DIR=node_modules/.bin

[mattszein]

Hey, i was facing same problem! I am using docker containers and a docker compose for development(not only production), and i found a solution.
The problem is a permissions issue related to how the container's temporary directory are mounted and configured. It needs to have exec permission.

So, In the rails service defined in my docker compose: I add this the exec permission to the tmp folder:

services:
  rails:
    ...
    tmpfs:
       - /tmp:exec

[dmarczal]

@mattszein Thanks for the reply.

I solved it by removing this option from docker-compose.yml:

  tmpfs:
    - /tmp

But is great to know it was just missing exec option.