The source post is mostly a pointer to an external 2024 tutorial, so it does not provide enough technical detail to freeze as a permanent Portainer recipe. Portainer itself has continued to evolve, and BigBearCasaOS still maintains a Portainer package today. The durable setup principles are simple: run the current Portainer CE image, persist /data, mount the Docker socket only if you intentionally want Portainer to control the local Docker engine, and protect the HTTPS management UI.
Current BigBearCasaOS lists Portainer as a maintained application, while current upstream Portainer CE documentation uses port 9443 for the HTTPS UI and a persistent portainer_data volume. Those current sources are safer than copying a two-year-old video command.
BigBearCasaOS Still Maintains Portainer
The current BigBearCasaOS repository continues to include Portainer and Portainer Agent packages. That means users who already trust and use the BigBear store can install the maintained app through CasaOS instead of manually reproducing the old tutorial.
See the current BigBearCasaOS application catalog.
Upstream Portainer Uses HTTPS on Port 9443 by Default
Current Portainer CE documentation says the server normally exposes:
-
9443— HTTPS management UI; -
8000— optional Edge Agent tunnel service.
Legacy HTTP port 9000 is optional and should not be opened simply because older tutorials used it.
Use the current Portainer CE Docker installation.
Persist Portainer's /data Directory
Portainer stores users, environments, endpoints, settings, and other management state under /data. If the container is recreated without persistent storage, the Portainer instance behaves like a new installation.
BigBear/CasaOS may use a host AppData folder while upstream examples use a named Docker volume. Either model is valid if the data survives container replacement.
The Docker Socket Gives Portainer Powerful Host Control
Mounting:
/var/run/docker.sock:/var/run/docker.socklets Portainer manage the local Docker engine. That is the feature users want—but it is also a powerful trust boundary. Anyone who takes over Portainer can often gain broad control over containers, mounted host files, and Docker-created privileged workloads.
Do Not Expose Portainer to the Internet Without Strong Protection
Keep Portainer on a trusted LAN, private VPN, or carefully protected reverse proxy. Use a strong administrator password, current image, and HTTPS. Do not publish an old unencrypted management port to the public Internet.
Portainer Does Not Replace CasaOS
CasaOS and Portainer can both manage the same Docker engine. That is useful for advanced inspection, stacks, networks, and volumes, but editing an app in Portainer can make the CasaOS App Store view disagree with the manually modified container.
For App Store applications, decide which manager is authoritative before making major configuration changes.
Update Portainer as a Stateful Application
Before updating, confirm /data is persistent and back it up when practical. Pull the new image, recreate the container with the same storage/socket mappings, and verify local-environment access afterward.
Portainer on CasaOS FAQ
Is the 2024 forum post itself a complete install guide?
No. It primarily links to an external BigBear tutorial.
Is BigBearCasaOS still maintaining Portainer?
Yes. The current BigBearCasaOS catalog still lists a maintained Portainer package.
Why is the Docker socket security-sensitive?
It gives Portainer direct control over the local Docker engine, which can translate into broad host-level power if the management UI is compromised.
