How mpepping/podshell works
Main Components Identification
a) Container Image Layer:
• User space environment (podshell user with UID 1000)
• Root access capability via sudo
b) Package Management Systems:
• Two parallel package managers:
• binenv (for GitHub releases)
• dbin (for Toolpacks repository)
c) Deployment Options:
• Kubernetes deployment paths
• Container runtime paths (Docker/Podman)
┌─ Kubernetes ─────────┐ ┌─ Container Runtimes ─┐
• Pod │ │ - Docker │
• Deployment │ │ - Podman │
• DaemonSet │ └────────────────────────┘
• ┘
┌─ Podshell Container ──────────────────────┐
• ┌─ User Space (UID 1000) ─────────────┐ │
• Regular user environment │ │
• Debugging tools │ │
• ┘ │
• ┌─ Package Managers ──────────────────┐ │
• ┌─ binenv ─┐ ┌─ dbin ────────┐ │ │
• GitHub │ │ Toolpacks │ │ │
• Releases │ │ Repository │ │ │
• ┘ └──────────────┘ │ │
• ┘ │
• ┘
┌─ Host System ────────────────────────┐
• Host PID │
• Host IPC │
• Host Network │
• Host Filesystem (/host mount) │
• ┘
Important Elements
• Regular user space (e.g., blue)
• Privileged components (e.g., red)
• Package management systems (e.g., green)
• Deployment options (e.g., orange)
• Container deployment flow
• Package installation paths
• Privilege escalation path (sudo)
• Host system access (for privileged mode)
Notes for Implementation
• Version tags for the container image
• GitHub container registry integration
• Configuration paths for sudoers and profile.d