Castopod
Stack
Castopod is a free and open-source hosting platform made for podcasters.
Services
app
Configuration
Imagecastopod/app:latest/opt/castopod/public/media : /portainer/Files/AppData/Config/castopod/appMYSQL_DATABASE=castopodMYSQL_USER=castopodMYSQL_PASSWORD=changemeCP_BASEURL=https://castopod.meCP_ANALYTICS_SALT=changemeCP_CACHE_HANDLER=redisCP_REDIS_HOST=redisalwaysImage details
web-server
Configuration
Imagecastopod/web-server:latest8848:80/var/www/html/media : /portainer/Files/AppData/Config/castopod/webunless-stoppedImage details
mariadb
Configuration
Imagemariadb/var/lib/mysql : /portainer/Files/AppData/Config/castopod/dbMYSQL_ROOT_PASSWORD=changemeMYSQL_DATABASE=castopodMYSQL_USER=castopodMYSQL_PASSWORD=changemealwaysImage details
redis
Configuration
Imageredis/data : /portainer/Files/AppData/Config/castopod/redisImage details
video-clipper
Configuration
Imagecastopod/video-clipper:latest/opt/castopod/public/media : /portainer/Files/AppData/Config/castopod/mediaMYSQL_DATABASE=castopodMYSQL_USER=castopodMYSQL_PASSWORD=changemealwaysImage details
Standalone Install
Select an install method, to see config/commands for deploying Castopod
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Castopod, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
app:
image: castopod/app:latest
container_name: Castopod-APP
volumes:
- /portainer/Files/AppData/Config/castopod/app:/opt/castopod/public/media
environment:
MYSQL_DATABASE: castopod
MYSQL_USER: castopod
MYSQL_PASSWORD: changeme
CP_BASEURL: https://castopod.me
CP_ANALYTICS_SALT: changeme
CP_CACHE_HANDLER: redis
CP_REDIS_HOST: redis
networks:
- castopod-app
- castopod-db
restart: always
web-server:
image: castopod/web-server:latest
container_name: Castopod-WEB-SERVER
volumes:
- /portainer/Files/AppData/Config/castopod/web:/var/www/html/media
networks:
- castopod-app
ports:
- 8848:80
restart: unless-stopped
mariadb:
image: mariadb
container_name: Castopod-DB
networks:
- castopod-db
volumes:
- /portainer/Files/AppData/Config/castopod/db:/var/lib/mysql
user: 1026:100
environment:
MYSQL_ROOT_PASSWORD: changeme
MYSQL_DATABASE: castopod
MYSQL_USER: castopod
MYSQL_PASSWORD: changeme
restart: always
redis:
image: redis
container_name: Castopod-REDIS
volumes:
- /portainer/Files/AppData/Config/castopod/redis:/data
user: 1026:100
networks:
- castopod-app
video-clipper:
image: castopod/video-clipper:latest
container_name: Castopod-VIDEO
volumes:
- /portainer/Files/AppData/Config/castopod/media:/opt/castopod/public/media
environment:
MYSQL_DATABASE: castopod
MYSQL_USER: castopod
MYSQL_PASSWORD: changeme
networks:
- castopod-db
restart: always
volumes:
castopod-media:
castopod-db:
castopod-cache:
networks:
castopod-app:
castopod-db:
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/castopod.yml up -dMore install options in our documentation.
Container Documentation
app Documentation
Castopod App bundle with all of its dependencies.
web-server Documentation
An Nginx configuration for Castopod.
mariadb Documentation
MariaDB Server is a high performing open source relational database, forked from MySQL.
redis Documentation
Redis is the world’s fastest data platform for caching, vector search, and NoSQL databases.
Serve Castopod 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 castopod.example.com to http://web-server:80
Add this to your Caddyfile
castopod.example.com {
reverse_proxy http://web-server: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:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8848 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8848 - Stop the other service, or pick a different host port. In
8848:80only 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:8848. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, castopod can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8848
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/castopod/app(and the same for the other mapped folders)
Image won't pull
Test the pull directly on the host: docker pull castopod/app: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 loginto 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.
- 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 always 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
noso 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.
- Bug within the app: Open an issue within castopod's repo
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Castopod is a Compose stack, a set of containers (5 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.
The services
This stack is built from 5 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
apprunscastopod/app:latestweb-serverrunscastopod/web-server:latestmariadbrunsmariadbredisrunsredisvideo-clipperrunscastopod/video-clipper:latest
Ports
A port is the door the app answers on. A mapping like 8848:80 means it's reachable on port 8848 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:8848 in a browser. It opens:
8848:80, likely the web interface
Volumes
A volume is where Castopod 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:
/opt/castopod/public/mediafrom/portainer/Files/AppData/Config/castopod/appon the host/var/www/html/mediafrom/portainer/Files/AppData/Config/castopod/webon the host/var/lib/mysqlfrom/portainer/Files/AppData/Config/castopod/dbon the host/datafrom/portainer/Files/AppData/Config/castopod/redison the host/opt/castopod/public/mediafrom/portainer/Files/AppData/Config/castopod/mediaon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Castopod takes 8 of them, all with defaults you can leave alone or tweak:
MYSQL_DATABASE, defaults tocastopodMYSQL_USER, defaults tocastopodMYSQL_PASSWORD, defaults tochangemeCP_BASEURL, defaults tohttps://castopod.meCP_ANALYTICS_SALT, defaults tochangemeCP_CACHE_HANDLER, defaults toredisCP_REDIS_HOST, defaults toredisMYSQL_ROOT_PASSWORD, defaults tochangeme
Restart policy
The restart policy here is always, so Docker brings Castopod back up after a crash and again when the server reboots. Good for anything you want running around the clock. 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
Portainer puts these services on one shared private network, so they can find each other by name (like app) while only the ports above are open to you.
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 Castopod up. Add the template list to Portainer once, then deploying Castopod is a click rather than a wall of config.