Portainer Templates logo

Portainer Templates

Gokapi Gokapi

Stack

Cloud

Gokapi is a lightweight server to share files, which expire after a set amount of downloads or days. It is similar to the discontinued Firefox Send, with the difference that only the admin is allowed to upload files

Image details

Pulls: 1.6M
Architecture: amd64, arm64, arm/v7, arm/v6, 386, riscv64
Image size: 23 MB
Latest: v2.2.4
User: f0rc3
Created: Mar 12, 2021
Updated: 1 month ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
f0rc3/gokapi:latest
Ports
53842:53842
Volumes
/app/data : /portainer/Files/AppData/Config/gokapi/data/app/config : /portainer/Files/AppData/Config/gokapi/config
Restart
on-failure:5
Source
Repo

Template by xneo1·Source

Standalone Install

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

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 Gokapi, 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:
  gokapi:
    container_name: Gokapi
    image: f0rc3/gokapi:latest
    ports:
      - 53842:53842
    volumes:
      - /portainer/Files/AppData/Config/gokapi/data:/app/data
      - /portainer/Files/AppData/Config/gokapi/config:/app/config
    restart: on-failure:5

Or deploy it directly from the source:

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

More install options in our documentation.

https://github.com/Forceu/Gokapi

Serve Gokapi 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 gokapi.example.com to http://gokapi:53842

Add this to your Caddyfile

gokapi.example.com {
	reverse_proxy http://gokapi:53842
}

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:53842 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :53842
  • Stop the other service, or pick a different host port. In 53842:53842 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:53842. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, gokapi can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 53842

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/gokapi/data (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull f0rc3/gokapi:latest

  • "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, arm/v7, arm/v6, 386, riscv64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

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

Gokapi 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 Gokapi needs bundled into one download. This template pulls f0rc3/gokapi:latest, which Docker fetches once (about 23 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Gokapi's comes from Docker Hub, published by f0rc3.

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.4. 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, arm/v7, arm/v6, 386, riscv64, 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 53842:53842 means it's reachable on port 53842 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 53842:53842

Volumes

A volume is where Gokapi 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:

  • /app/data from /portainer/Files/AppData/Config/gokapi/data on the host
  • /app/config from /portainer/Files/AppData/Config/gokapi/config on the host

Restart policy

The restart policy here is on-failure:5, so Gokapi won't come back on its own after a crash or reboot. You bring it up again whenever you're ready. 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 Gokapi 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 gokapi. That's what you'll spot in the containers list and use in commands like docker logs gokapi.

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 Gokapi up. Add the template list to Portainer once, then deploying Gokapi is a click rather than a wall of config.