Multiplatform builds for Memos, a beautiful, lightweight, and privacy-first note-taking service.

Some of these builds are utilized by Memospot, a self-contained desktop app for Memos, available on macOS, Linux, and Windows.

This project also provides optimized Memos images for the following platforms:

To use an image for a specific CPU architecture, add --platform=<platform> to the docker command line, before the image specifier. Read more at Platform variants.

docker run --detach --name memos --publish 5230:5230 \
  --volume ~/.memos/:/var/opt/memos lincolnthalles/memos:latest

docker run --detach --name memos-nightly --publish 5231:5230 \
  --volume ~/.memos-nightly/:/var/opt/memos lincolnthalles/memos:nightly

docker run --detach --rm --name memos-throwaway --publish 5232:5230 \
  --env MEMOS_MODE=demo lincolnthalles/memos:nightly

Use Watchtower.

docker run --detach --name watchtower \
  --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower

• Versioned images are checked out to the matching Memos upstream tag.

• Nightly images use whatever is available at Memos main branch at build time.

• Image packages are auto-upgraded at build time.

• Nightly images are built daily at 00:00 UTC.

• Images are published at the same time to Docker Hub and GitHub Container Registry.

Up to v0.19.0, arm32v5 images were based on debian:stable-slim.

There are multiple builds for arm and amd64 platforms, with different hardware optimizations. Choose the one that best suits the host CPU.

Run cat /proc/cpuinfo and uname -m to find out your CPU model and architecture. For an ARMv8 or aarch64 CPU, use the ARM64 build.

⚠ Avoid using the arm/v5 variant unless the host CPU can't handle anything newer. While it works, the lack of VFP hinders the performance of applications that were not specifically written to this architecture.

Linux binaries are packed with UPX. This may trigger false positives on some antivirus software. You can unpack the binaries with upx -d memos*, if you will.

It's currently not possible to build Memos for Windows i386 and any sort of MIPS architecture, because modernc.org/libc (used by SQLite driver) is not compatible with these targets.

Memos official first-class support is for its Docker container. These binaries and images are provided as a convenience for some specific use cases. They may work fine, and they may not. Use them at your discretion.

Please do not open issues on the official Memos repository regarding these builds, unless you can reproduce the issue on the official Docker container.

You should manually set up a system service to start Memos on boot.

Memos Service Guide

Memos Windows Service Guide

To run Memos using Termux on Android:

• Download a Linux build suiting device CPU architecture (most modern devices are arm64)

• Extract the downloaded file and copy the memos binary to internal storage

Run this on Termux:

# This will prompt you for storage access permission
termux-setup-storage

# Copy the binary to Termux home directory
cp ~/storage/shared/memos .

# Make it executable
chmod +x ./memos

# Run Memos
MEMOS_MODE=prod MEMOS_DATA=. MEMOS_PORT=5230 ./memos

# Memos will be available at http://localhost:5230
# and on local network at http://<device-ip>:5230

⚠ As stated at Termux Wiki, all data under Termux's home directory will be deleted if you uninstall the app.

If you appreciate this project, be sure to ⭐star it on GitHub.