Docker builds for Linux ARM64

[skyfallwastaken]

It would be great if there were Docker builds for Linux ARM64, so folks with ARM servers can use Fizzy!

[BernhardMillauerAdventics]

For some not explained reason the arm image build was disabled: #1804

Coolify just added the service and usually coolify runs on raspberry, so a arm build/image would be awesome!
coollabsio/coolify#7468

[mike-weiner]

I've asked over in #1804 to see if we can get some context as to why arm builds were disabled: #1804 (comment)

I was hoping to deploy onto a Raspberry Pi.

[dakotahp]

If we get any information on what is blocking then the community can help get it to a state where it can be readded. As it is, we're working blind since it all seems to be working fine. I have plenty of docker experience but image architecture is one thing I haven't messed with. I threw it to Cursor to see if it could build it for Apple Silicon in a way that I can verify. It came up with a test script here that others can try: https://github.com/dakotahp/fizzy/pull/1/changes#diff-b817a03f9af94fd5122c29a8e8eda20f4bfb6550a3f7e07d7d3272bd8908fd8f

The gist is that the Dockerfile already is set up for dynamic architecture, and the bundle process works fine for me. I didn't experience any ruby gem failures to compile. That said, it is possible that maybe the dockerfile is picking up on the gems being bundled locally on my machine prior to trying to build the Dockerfile.

Any other things that sound actionable to anyone for next steps?

[SeriousM]

For now you can use this snippet to build it during deployment:

services:
  fizzy:
    build:
      context: 'https://github.com/basecamp/fizzy.git#main'
      dockerfile: Dockerfile
    environment:
....

This will pull the repository and use the original docker file to build on your arm64 with success!

[pachieh]

Any updates on this? I can get it to run but only through Rosetta emulation. Here is my .yml...

services:
web:
image: ghcr.io/basecamp/fizzy:main
platform: linux/amd64
restart: unless-stopped
ports:
- "4001:4001"
environment:
- HTTP_port=4001
- SECRET_KEY_BASE=abcdefabcdef
- TLS_DOMAIN=localhost
- DISABLE_SSL=true
- BASE_URL=http://localhost
- MAILER_FROM_ADDRESS=fizzy@example.com
- SMTP_ADDRESS=mail.example.com
- SMTP_USERNAME=user
- SMTP_PASSWORD=pass
- VAPID_PRIVATE_KEY=myvapidprivatekey
- VAPID_PUBLIC_KEY=myvapidpublickey
volumes:
- fizzy:/rails/storage

volumes:
fizzy:

[estevao]

Below is what I have working on Mac mini M1 and AWS Graviton with Ubuntu Server 2024. It's building cleanly, no issues so far.

Note: This config assumes you cloned fizzy repo on ~/code/fizzy - good for dev/quick code changes. Alternatively, change context and dockerfile as showed in previous post.

services:
  fizzy:
    build:
      # Switch to your local code directory
      context: /Users/<your_user>/code/fizzy
      dockerfile: Dockerfile
    container_name: fizzy
    platform: linux/arm64
    restart: unless-stopped
    environment:
      RAILS_ENV: production
      SECRET_KEY_BASE: <secret_key>
      BASE_URL: <base_url>
      DISABLE_SSL: "true"
      RAILS_HOSTS: localhost,127.0.0.1
      RAILS_SERVE_STATIC_FILES: "true"
      SMTP_ADDRESS: smtp.gmail.com
      SMTP_PORT: 587
      SMTP_USERNAME: <your_email>@gmail.com
      SMTP_PASSWORD: <your_gmail_app_passwd>
      SMTP_AUTHENTICATION: plain
      SMTP_ENABLE_STARTTLS_AUTO: "true"
      SMTP_SSL: "false"
      SMTP_OPENSSL_VERIFY_MODE: none
      MAILER_FROM_ADDRESS: fizzy@fizzy.localhost
    volumes:
      # 1. Main bind mount for code sync
      - /Users/<your_user>/code/fizzy:/rails

      # 2. Anonymous volumes to prevent overwriting container-built dependencies
      #    This ensures the Linux gems and precompiled assets remain visible.
      - /rails/node_modules
      - /rails/vendor/bundle
      - /rails/public/assets
      - /rails/tmp

      # 3. Preserve persistent storage
      - ~/.fizzy:/rails/storage
    networks:
      - shared-proxy-network
    mem_limit: 2g
    mem_reservation: 512m

networks:
  shared-proxy-network:
    external: true
    name: shared-proxy-network

[pavelklymenko]

Perfect. Thank you!

[SamuelAierizer]

But is someone actively working on making sure ARM is compatible and doing adjustments so we can add back the default image build? I will gladly look at it if nobody else did until now. Or is this a decision from the Fizzy team that we will not be adding these back?

[kevinmcconnell]

We've added arm64 back to the default image (#2422). It had been initially disabled due to some build failures, but it's been on our list to add it back again.

Should be all set now, but let us know if you run into any issues!