tailwindcss: [V4] Illegal instruction when using beta inside Docker
What version of Tailwind CSS are you using?
v4 beta 9
What build tool (or framework if it abstracts the build tool) are you using?
docker and ruby
What version of Node.js are you using?
🤷
What browser are you using?
For example: N/A
What operating system are you using?
linux
Reproduction URL
Dockerfile
# syntax=docker/dockerfile:1
# check=error=true
FROM docker.io/library/ruby:3.4.1-slim AS base
RUN apt-get update -qq && \
apt-get install --no-install-recommends -y curl build-essential git pkg-config && \
rm -rf /var/lib/apt/lists /var/cache/apt/archives
RUN curl -L -o bin/tailwindcss https://github.com/tailwindlabs/tailwindcss/releases/download/v4.0.0-beta.2/tailwindcss-linux-x64 && \
chmod a+x ./bin/tailwindcss
RUN ./bin/tailwindcss --help
command: docker buildx build --platform linux/amd64 --file Dockerfile.tw .
Describe your issue
When trying to execute the beta executable in x86 for linux, it errors with ‘0.054 Illegal instruction’
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 9
- Comments: 20 (6 by maintainers)
This will be fixed in the next patch release going out today. Thanks again everyone for your help in testing this!
Thank you for all your testing, really appreciate it. Let us get this out asap now 👍
Hey folks! I prepared a PR (#16244) that uses a different bun base that compiles to a reduced instruction set and with that I was able to fix the Dockerfile repro:
Since it’s a bit hard for us to test across different server setups mentioned above I wanted to ask for your help to figure out if this resolves (at least some) of the issues.
Excuse the unconventional way of deploying the binary but I’ve uploaded preview builds here:
@pzgz I think the intention was to try the
-linux-x64binary if you’re on a GNU libc system, and the-linux-x64-muslbinary if you’re on a Musl libc system (like Alpine).Fwiw that repro dockerfile up above was being run using orbstack on an m2 mac
I’ve had several users of the downstream package
tailwindcss-rubycomplain about issues that seem like they may be caused by this:@philipp-spiess tagging you because you were involved in the bun Musl support conversation and may have some insight?
If it’s helpful, so far the users that have reported the issue are on various hardware: