GlinrDock is a lightweight container management platform that provides a web interface for managing Docker containers and Docker Compose projects. It offers team collaboration features, monitoring, and deployment capabilities.
- Lightweight: Minimal resource usage compared to Kubernetes
- Docker Compose compatible: Import existing compose files
- Team-focused: Built-in multi-user support and RBAC
- Easy setup: 30-second installation process
- Production-ready: Zero-downtime deployments and monitoring
GlinrDock offers:
- Free tier: Personal projects and development use
- Commercial licenses: For production and enterprise use
- See our pricing at https://glincker.com/pricing
The source code is maintained in a private repository. This public repository contains only binary distributions, documentation, and installation scripts.
Minimum:
- Linux kernel 3.10+ or macOS 10.15+
- Docker Engine 20.10+
- 512MB RAM
- 1GB disk space
Recommended:
- 2GB+ RAM
- 10GB+ disk space
- SSD storage
- systemd (Linux)
No, GlinrDock requires Docker Engine to manage containers. However, you can run GlinrDock itself as:
- Native binary (recommended for Linux)
- Docker container (easier deployment)
Use the automated installer which detects your architecture:
curl -fsSL https://github.com/GLINCKER/glinrdock-release/releases/latest/download/install.sh | sudo bashOr download the appropriate binary manually:
glinrdockd_darwin_arm64.tar.gzfor Apple Siliconglinrdockd_linux_arm64.tar.gzfor ARM64 Linux
The automated installer requires root privileges to:
- Install to
/usr/local/bin - Create systemd service
- Set up system user
For non-root installation:
- Download binary manually
- Run in user space
- Use Docker installation method
Linux installation:
Edit /etc/glinrdock/config.toml:
[server]
bind_addr = "127.0.0.1:9090"Docker installation:
docker run -p 9090:8080 ...Linux installation:
- Configuration:
/etc/glinrdock/ - Data:
/var/lib/glinrdock/ - Logs:
journalctl -u glinrdockd
Docker installation:
- Data volume:
glinrdock_data - Container logs:
docker logs glinrdock
Linux:
sudo tar czf glinrdock-backup.tar.gz -C /var/lib/glinrdock .Docker:
docker run --rm -v glinrdock_data:/data -v $(pwd):/backup alpine tar czf /backup/glinrdock-backup.tar.gz -C /data .Generate new token:
openssl rand -hex 32Linux installation:
sudo sed -i 's/admin_token = .*/admin_token = "NEW_TOKEN_HERE"/' /etc/glinrdock/config.toml
sudo systemctl restart glinrdockdDocker installation:
docker run -e GLINRDOCK_ADMIN_TOKEN="NEW_TOKEN_HERE" ...Yes! GlinrDock supports importing Docker Compose files:
- Go to Projects → Import
- Upload your
docker-compose.ymlfile - Review and deploy
Use GlinrDock's project-based organization:
- Create separate projects for dev/staging/prod
- Use environment variables for configuration
- Deploy to different Docker networks
Yes, configure registry credentials in:
- Settings → Registries
- Add registry URL, username, and password
- GlinrDock will authenticate automatically
Currently, GlinrDock focuses on single-node Docker and Docker Compose deployments. Swarm and Kubernetes support are planned for future releases.
Check what's using port 8080:
sudo netstat -tlnp | grep 8080Solutions:
- Kill the conflicting process
- Change GlinrDock's port (see configuration above)
- Use a different port:
-p 8081:8080(Docker)
Check Docker is running:
sudo systemctl status docker
sudo systemctl start dockerCheck permissions:
# Add user to docker group
sudo usermod -aG docker $USER
# Log out and back in
# Or for GlinrDock user (Linux installation)
sudo usermod -aG docker glinrdock
sudo systemctl restart glinrdockdCheck admin token:
# Linux
sudo grep admin_token /etc/glinrdock/config.toml
# Docker
docker logs glinrdock | grep "Admin token"Clear browser cache:
- Hard refresh (Ctrl+F5)
- Clear browser data
- Try incognito/private mode
Linux installation:
Edit /etc/glinrdock/config.toml:
[logging]
level = "debug"Docker installation:
docker run -e GLINRDOCK_LOG_LEVEL="debug" ...View logs:
# Linux
sudo journalctl -u glinrdockd -f
# Docker
docker logs -f glinrdockGlinrDock can manage hundreds of containers, limited primarily by:
- Available system resources (RAM, CPU)
- Docker daemon performance
- Network and storage I/O
No, GlinrDock acts as a management layer and doesn't impact container runtime performance. It uses the Docker API for all operations.
- Binary installation: 50-100MB
- Docker installation: 100-200MB (including base image)
- Memory usage scales with number of managed containers
Not recommended without proper security measures:
- Use HTTPS with valid certificates
- Implement strong authentication
- Use firewall and access controls
- Consider VPN access
Better approach:
- Keep on private network
- Use VPN or SSH tunneling for remote access
- Implement reverse proxy with authentication
The Docker socket provides root-equivalent access. Security options:
- Use TCP with TLS (advanced):
dockerd --host=tcp://127.0.0.1:2376 --tls --tlscert=... --tlskey=...- Restrict socket permissions:
sudo chmod 660 /var/run/docker.sock- Use Docker-in-Docker (more complex setup)
- Documentation: Check our comprehensive docs
- GitHub Issues: Report bugs or feature requests
- Community: GitHub Discussions for questions
- Enterprise: Contact support@glincker.com
DO NOT use public GitHub issues for security vulnerabilities.
Email: security@glincker.com
See our Security Policy for details.
- Patch releases: Monthly (bug fixes)
- Minor releases: Quarterly (new features)
- Major releases: Yearly (breaking changes)
- Security updates: As needed
While the source code is private, you can contribute by:
- Reporting issues and feature requests
- Improving documentation
- Sharing usage examples
- Providing feedback
- Export your Docker Compose files from Portainer
- Install GlinrDock
- Import compose files into GlinrDock projects
- Verify deployments and remove Portainer
Yes, GlinrDock uses standard Docker APIs and can coexist with other tools. However, avoid simultaneous management of the same containers to prevent conflicts.
Linux installation:
curl -fsSL https://github.com/GLINCKER/glinrdock-release/releases/latest/download/install.sh | sudo bashDocker installation:
docker-compose pull
docker-compose up -dData and configuration are preserved during upgrades.
Still have questions?
- Check our Troubleshooting Guide
- Ask in GitHub Discussions
- Contact support@glincker.com