One-Click Install Prompt Hub中文

Portainer CE

Container and Docker environment management dashboard.

Category Other Self-hostedPlatforms DockerPrivileges Host Docker accessChinese docs Many Chinese tutorialsStars ~39K

One-click install command

docker volume create portainer_datandocker run -d -p 8000:8000 -p 9443:9443 \n  --name portainer --restart=always \n  -v /var/run/docker.sock:/var/run/docker.sock \n  -v portainer_data:/data portainer/portainer-ce:lts

Notes

Mounting docker.sock is high-privilege and risky; port 8000 is only needed for Edge Agent. Officially geared toward homelab and non-critical production.

Agent Prompt

Copy the block below and hand it to an AI Agent — replace [bracketed] parts with your own values.

Deploy Portainer CE (Container and Docker environment management dashboard) in my environment.

Before starting:
1. Run read-only checks first: OS version, CPU architecture, available disk/RAM, port usage, Docker or sudo access — and report the findings.
2. Use the project source https://github.com/portainer/portainer as ground truth; verify the current stable version, prerequisites and compatibility.
3. Present an execution plan, the files/services/firewall rules to be changed, and a complete rollback plan; wait for my confirmation before executing.
4. Download remote scripts locally for review first; pin tag / image digest / commit; don't rely on latest or master.
5. Never put secrets (passwords, API keys, tokens, subscription URLs) in the prompt, shell history or logs — use 600-permission env files, Docker secrets or _FILE variables instead.

Verified starting command (don't run blindly — download/expand and review first):
docker volume create portainer_datandocker run -d -p 8000:8000 -p 9443:9443 \n  --name portainer --restart=always \n  -v /var/run/docker.sock:/var/run/docker.sock \n  -v portainer_data:/data portainer/portainer-ce:lts

Project-specific notes:
- Mounting docker.sock is high-privilege and risky; port 8000 is only needed for Edge Agent. Officially geared toward homelab and non-critical production.
- Permission requirement: Host Docker access. Don't escalate privileges; don't run containers as root unnecessarily.

After execution, verify and report back:
- Installed version, service status and health check results;
- Open ports, listen addresses, firewall changes;
- Config files, data volumes, log and backup locations;
- Access method (for sensitive credentials, only state where they're stored — never print them);
- Restart policy, plus verified uninstall / rollback commands.

Related tools