Portainer Templates logo

Portainer Templates

Appsmith Appsmith

Stack

ProductivityDevelopmentLow Code

Appsmith (www.appsmith.com) is the first open-source low-code tool that helps developers build dashboards and admin panels very quickly.

Image details

Pulls: 20.0M
Architecture: amd64, arm64
Image size: 1.3 GB
Latest: v2.2
User: shrikantappsmith
Created: Sep 15, 2021
Updated: 4 hours ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
index.docker.io/appsmith/appsmith-ce
Ports
1810:801443:443
Volumes
/appsmith-stacks : /portainer/Files/AppData/Config/appsmith
Restart
unless-stopped
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Appsmith

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Appsmith, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  appsmith:
    image: index.docker.io/appsmith/appsmith-ce
    container_name: appsmith
    ports:
      - "1810:80"
      - "1443:443"
    volumes:
      - /portainer/Files/AppData/Config/appsmith:/appsmith-stacks
    restart: unless-stopped
    # Uncomment the lines below to enable auto-update
    #labels:
    #  com.centurylinklabs.watchtower.enable: "true"

  #auto_update:
  #  image: containrrr/watchtower
  #  volumes:
  #    - /var/run/docker.sock:/var/run/docker.sock
  #  # Update check interval in seconds.
  #  command: --schedule "0 0 * ? * *" --label-enable --cleanup
  #  restart: unless-stopped
  #  depends_on:
  #    - appsmith
  #  environment:
  #    - WATCHTOWER_LIFECYCLE_HOOKS=true

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/appsmith.yml up -d

More install options in our documentation.

Notice: We recommend using appsmith/appsmith-ee instead of this image for the following reasons:
  • The appsmith/appsmith-ee image includes a free plan that is feature-compatible with the community version.
  • The appsmith/appsmith-ee image allows you to trial the paid features and upgrade with a single click.

To enjoy a smoother and more robust experience, we encourage all users to start with appsmith/appsmith-ee.
Please visit https://docs.appsmith.com/getting-started/setup/installation-guides/docker⁠ to learn how to use this image to run your Appsmith instance.

Serve Appsmith on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying appsmith.example.com to http://appsmith:80

Add this to your Caddyfile

appsmith.example.com {
	reverse_proxy http://appsmith:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:1810 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :1810
  • Stop the other service, or pick a different host port. In 1810:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:1810. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, appsmith can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 1810

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/appsmith

Image won't pull

Test the pull directly on the host: docker pull index.docker.io/appsmith/appsmith-ce

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Appsmith is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Appsmith needs bundled into one download. This template pulls index.docker.io/appsmith/appsmith-ce, which Docker fetches once (about 1.3 GB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Appsmith's comes from index.docker.io, published by appsmith.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v2.2. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 1810:80 means it's reachable on port 1810 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:1810 in a browser. It opens:

  • 1810:80, likely the web interface
  • 1443:443, likely the web interface

Volumes

A volume is where Appsmith keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /appsmith-stacks from /portainer/Files/AppData/Config/appsmith on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Appsmith after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Appsmith sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container appsmith. That's what you'll spot in the containers list and use in commands like docker logs appsmith.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Appsmith up. Add the template list to Portainer once, then deploying Appsmith is a click rather than a wall of config.