Self-Hosting Penpot on ARM64 VPS: Guide to Overcome Architecture Compatibility Issues for Custom UI/UX Design Platform
This guide provides a detailed walkthrough to self-host Penpot — an open-source UI/UX design platform — on ARM64 VPS, overcoming hardware and software architecture compatibility...
This guide provides a detailed walkthrough to self-host Penpot — an open-source UI/UX design platform — on ARM64 VPS, overcoming hardware and software architecture compatibility issues. It covers Docker setup, environment variables, handling incompatible binaries, and performance optimization for production use. Penpot offers a self-hosted alternative to cloud-based design tools, enabling businesses to maintain full control over design data and customize the user interface.
Introduction to Penpot and Benefits of Self-Hosting
Penpot is an open-source UI/UX design platform compatible with Figma, allowing users to create, edit, and share visual designs without relying on cloud services. Self-hosting Penpot on an ARM64 VPS offers significant advantages, including data control, internal security, lower operational costs, and high customization. However, since Penpot is primarily built for x86_64 architecture, deployment on ARM64 systems (such as Apple Silicon or ARM64 VPS) often encounters compatibility errors related to binary incompatibility.
Overcoming these architecture compatibility issues is critical for stable Penpot operation on ARM64 platforms. This guide provides practical solutions using Docker, environment configuration, and reconfiguring dependencies to ensure Penpot runs smoothly on ARM64 VPS.
Prerequisites and Initial Setup
To deploy Penpot on an ARM64 VPS, you need a server with ARM64 architecture (e.g., Raspberry Pi 4, ARM64 server, or VPS available at NVMe Cloud VPS for Docker, Nginx & Databases). The basic requirements include:
- OS: Ubuntu 22.04 or Debian 11 (ARM64)
- Docker and Docker Compose installed
- Required software: curl, git, and a port manager like Nginx or Caddy
- Hardware: Minimum 4GB RAM, 2 vCPU, 20GB SSD
Prepare the system by updating packages and installing Docker:
sudo apt update
sudo apt install -y curl git
curl -sSL https://get.docker.com | sh
sudo usermod -aG docker $USER
sudo systemctl enable docker
After logging back in, verify Docker is working:
docker --version
docker compose version
Deploying Penpot with Docker on ARM64
Penpot uses Docker Compose to manage services such as Web, API, Redis, PostgreSQL, and File Storage. However, default images may not support ARM64. To resolve this, use ARM64-compatible images or build from source.
First, create a working directory and copy the `docker-compose.yml` file from the official Penpot repository. Since default images are incompatible, replace them with ARM64-compatible alternatives.
Replace the image lines in `docker-compose.yml` with ARM64-compatible images:
services:
web:
image: penpot/penpot-web:latest-arm64
# ... other configurations
api:
image: penpot/penpot-api:latest-arm64
# ... other configurations
Instead of using `latest`, use specific versions or build images from source. You can create a custom Dockerfile to rebuild components for ARM64:
FROM penpot/penpot-web:latest
# ARM64-specific build steps
Start the deployment:
docker compose up -d
Penpot will start, but check logs to identify architecture-related errors.
Handling Architecture Compatibility Errors
During deployment, you may encounter errors like `exec format error` or `no such file or directory`, indicating binary incompatibility with ARM64 architecture. These issues often affect components like Node.js, PostgreSQL, or Redis.
To resolve them:
- Replace default images with ARM64-compatible ones. Search Docker Hub for images with prefixes like `arm64v8` or `linux/arm64`.
- Use `docker buildx` to build images from source on ARM64:
docker buildx build --platform linux/arm64 -t penpot-web-arm64 .
Ensure all dependencies are built or use compatible images. Services like Redis and PostgreSQL may require specific ARM64 configurations.
Verification and Optimization
After Penpot starts, access the VPS IP or domain to verify the user interface. Verification steps include:
- Visit
http://your-vps-ip:3000and log in with the default account. - Create a new design to test functionality.
- Run
docker compose psto check service status.
To optimize performance, consider:
- Adding Nginx as a reverse proxy with HTTPS support.
- Setting up Redis as a cache for API requests.
- Running services like PostgreSQL on a separate VPS to offload load.
Penpot also supports integration with Git and CI/CD tools, enabling design management like source code.
Alternative Solutions and Recommendations
If building ARM64 images is too complex, consider alternatives such as:
- Deploying Penpot on x86_64 VPS if available.
- Using cloud services like Powerful VPS Ideal for Cyber Range Network Experimentation to run Penpot on x86_64 infrastructure.
- Referencing guides on building a residential proxy system on 20 cheap VPS for insights into multi-server deployments.
Self-hosting Penpot on ARM64 requires basic DevOps skills but offers high control and customization. With correct configuration, Penpot can operate reliably as an independent UI/UX design platform.
Recommended NVMe Cloud VPS Plans to Deploy This Setup
Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.
VPS-3E
10% VAT included
- CPU: 2 vCPU
- RAM: 4 GB
- SSD: 50 GB NVMe
