Tailwind 4: Can't compile on Docker linux/amd64

[dixpac]

After upgrading to latest version 4, I have noticed that building tailwindcss errors out:

I'm building this docker image from mac, but for linux/amd64 arch.
docker build -t cmp --platform linux/amd64 .

This works fine on older tw versions 3.xx, but not on the latest version 4.

Here is the reproduction repo. In this repo there are 2 branches

• main - runs on tailwind 3
• tw4 - runs latest tailwind 4

Running docker build -t cmp --platform linux/amd64 . on main branch will work, on branch tw4 will fail.

Reproduction repo is vanilla rails app(rails new cmp ----css tailwind ) with 1 scaffold(user).

[flavorjones]

Thanks for reporting, I'll take a look.

[flavorjones]

@dixpac I can't reproduce what you're seeing, unfortunately. This works fine for me:

bepi in tailwind-docker-issue on  tw4 via 💎 v3.3.5
$ docker build --platform linux/amd64 .
[+] Building 57.4s (20/20) FINISHED                                                                   docker:default
 => [internal] load build definition from Dockerfile                                                            0.0s
 => => transferring dockerfile: 2.38kB                                                                          0.0s
 => resolve image config for docker-image://docker.io/docker/dockerfile:1                                       0.4s
 => [auth] docker/dockerfile:pull token for registry-1.docker.io                                                0.0s
 => CACHED docker-image://docker.io/docker/dockerfile:1@sha256:93bfd3b68c109427185cd78b4779fc82b484b0b7618e36d  0.0s
 => [internal] load metadata for docker.io/library/ruby:3.3.5-slim                                              0.0s
 => [internal] load .dockerignore                                                                               0.0s
 => => transferring context: 916B                                                                               0.0s
 => [base 1/3] FROM docker.io/library/ruby:3.3.5-slim                                                           0.0s
 => [internal] load build context                                                                               0.0s
 => => transferring context: 109.48kB                                                                           0.0s
 => [base 2/3] WORKDIR /rails                                                                                   0.0s
 => [base 3/3] RUN apt-get update -qq &&     apt-get install --no-install-recommends -y curl libjemalloc2 lib  14.7s
 => [build 1/6] RUN apt-get update -qq &&     apt-get install --no-install-recommends -y build-essential git   14.2s
 => [build 2/6] COPY Gemfile Gemfile.lock ./                                                                    0.0s
 => [build 3/6] RUN bundle install &&     rm -rf ~/.bundle/ "/usr/local/bundle"/ruby/*/cache "/usr/local/bund  17.0s
 => [build 4/6] COPY . .                                                                                        0.0s
 => [build 5/6] RUN bundle exec bootsnap precompile app/ lib/                                                   0.5s
 => [build 6/6] RUN SECRET_KEY_BASE_DUMMY=1 ./bin/rails assets:precompile                                       1.1s
 => [stage-2 1/3] COPY --from=build /usr/local/bundle /usr/local/bundle                                         0.6s
 => [stage-2 2/3] COPY --from=build /rails /rails                                                               0.4s
 => [stage-2 3/3] RUN groupadd --system --gid 1000 rails &&     useradd rails --uid 1000 --gid 1000 --create-h  6.2s
 => exporting to image                                                                                          0.8s
 => => exporting layers                                                                                         0.8s
 => => writing image sha256:6672869394f2219c5f4bca0211e4bf4ad09951af19865c7a9bbce6633e3b23f5                    0.0s

So we can do a couple of things here ... I'm curious what the differences are between our systems. I'm running on an intel Linux machine. 🤷

Here's another thing I'd like to ask you to do.

1. Shell into that container, built with all the layers up to the failing one. You may have to comment out the precompile step to get the tag to pass to docker run -it cmp /bin/bash.
2. Run bundle exec tailwindcss --help

Does that process print out something like this?

rails@909bab758810:/rails$ bundle exec tailwindcss --help
["/usr/local/bundle/ruby/3.3.0/gems/tailwindcss-ruby-4.0.0-x86_64-linux-gnu/exe/x86_64-linux-gnu/tailwindcss", "--help"]
≈ tailwindcss v4.0.0

Usage:
  tailwindcss [--input input.css] [--output output.css] [--watch] [options…]

Options:
  -i, --input ··········· Input file
  -o, --output ·········· Output file [default: `-`]
  -w, --watch ··········· Watch for changes and rebuild as needed
  -m, --minify ·········· Optimize and minify the output
      --optimize ········ Optimize the output without minifying
      --cwd ············· The current working directory [default: `.`]
  -h, --help ············ Display usage information

I'm curious if for some reason the upstream binary that this gem packages won't run in the container on your machine (and if it doesn't we can probably report it upstream and let them and the bun team figure it out).

[dixpac]

Here is what i get connecting to a container:

I'm running on MacBook M chip:

I'm curious if for some reason the upstream binary that this gem packages won't run in the container on your machine (and if it doesn't we can probably report it upstream and let them and the bun team figure it out).

Yeah! From the main branch works like a charm, but tw4 doesn't

ps
I will upload zipped docker image I've build locally when I'm back home its 730MB and upload speed where I'm at currently is low.

[flavorjones]

Looks like you might be seeing a known bug with the CLI: tailwindlabs/tailwindcss#15181

[dixpac]

Yup!

[flavorjones]

Should be fixed in https://github.com/flavorjones/tailwindcss-ruby/releases/tag/v4.0.4