Refactor & Function Bump: Docker

[MickLesk]

✍️ Description

• Refactor
• Adding Features:
• 1. Install Compose v2 Plugin
• 2. Portainer
• 3. Portainer Agent (only if Portainer not installed)
• 4. Expose Docker TCP Socket - Local, No, All Interfaces
• Update-Script Refactor - autom. Crawling if Portainer / Agent Installed / Docker V2 Installed -> Update this

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

[Ivoz]

Hi @MickLesk , I was reading this change, and I noticed. The install script runs $STD sh <(curl -fsSL https://get.docker.com). Docker's install script, by default, already installs the docker-compose-plugin package, which comes from docker's sources, not debian's. I'd assume, coming from docker's sources, it would already be relatively up-to-date and compatible with the rest of the docker stack installed. For instance, I just installed this package on a new Trixie install on an RPi; docker-compose-plugin shows to be 2.40.3, which is the same as the current release in https://github.com/docker/compose/releases

So I'd postulate that maybe one doesn't need to manually re-install any other docker compose plugin as the script currently does (unless the get.docker.com sh file changes drastically in the future)