-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to install on M1 (running in a container) #104
Comments
@wdiechmann - Sorry you're having a problem, I'll try to help. Inside your docker container, what does |
oh no - don't be sorry - it's me being sorry not able to offer any help solving this (giving back just something to the community) - but I'll take that help any given (Monday) 🤣
|
I guess I'm on my way to "the land of containers" -- pulling the finer print on the container underlines that tailwindcss-rails is entirely without fault (I think)
|
@wdiechmann OK, since your version of Ruby says it's Your best bet is to follow the instructions at https://tailwindcss.com/docs/installation to install tailwindcss via npm. |
well - roger that - but I'm not going down the npm gauntlet again 🤣 not with this beautiful piece of 'ware letting out sirene songs from those cliffs up high 😄 but thx a bunch for holding my hand and administering a cold handkerchief on my forehead ❤️ |
BTW - this docker/for-linux#1170 confirms it and now I just have to find out how to impersonate the correct platform for tailwindcss to ask for it certainly is xmas all around 😌 |
I'm addressing the issue here - placing all my faith in the "Gods of Container Heaven" |
I think we can close this @dhh |
For good measure: SOLVED! build the container "by hand" - using
|
I ran into the same problem and the above didnt work for me (perhaps I didnt follow all the steps) Specifically I get the error Digging into this gems code we can see it compares the platform with the matching executable
It seems that the My fix was to bypass the rails command and run the executable directly using something like this:
|
I still can't get it working, and I'm very confused by the above. If my architecture is ARM, why do I want to force it to install x86_64 binaries? Won't that end up running everything more slowly, under Rosetta 2 (and breaking completely when Apple discontinues that)? |
Please make sure you're on the most recent version of Bundler. If you're still having problems, please open a new issue and we can dig in together. |
Let me start by apologizing for 'fuming in the wrong kitchen' (this is not tailwindcss-rails per se - I actually anticipate it doing exactly what it should! It's much more likely some Docker container "thing" that lures the container into reporting "aarch64-linux" which I -- by now -- have learned repeatedly, is not a supported architecture by tailwindcss-rails !
Reckoning me not being alone on this crusade I risk the barrage and go forth:
Question: Does anyone know how to get Rails 7.0.0 to install with TailwindCSS in containers on the Apple M1 ?
the sordid details
Apple's latest/finest 'sand' - the M1 - is screaming fast but somewhat of a challenge to run Docker containers on;
Like with the sparkling fresh Rails 7.0.0 when doing
rails new . --css=tailwind
I have a Dockerfile like this
[ update: 2021-12-20 22:30 CEST: the from image is actually arm64v8/ruby ]
and a docker-compose.yml like this (the db part is merely for completeness - it serves no purpose in this trickery
When I let it 'rip' -- hoping to install tailwindcss goodness after the fact (it failed during the initial
rails new
too ) -- I get this sad reply:but for some reason the container keeps 'bragging about being' aarch64-linux 😆
So - now my heading (and my bearing for that matter too) is somewhat lost!
How do I get my containers to swallow their (linux) pride and start behaving?
The text was updated successfully, but these errors were encountered: