Hagicode Container
Deploy quickly with Docker Compose Builder, simple configuration, ready to use
Why Choose Container Deployment?
Environment Isolation
Containerized deployment avoids dependency conflicts, doesn't affect system environment, keeps system clean
Simple Configuration
Use Docker Compose Builder for visual configuration, no need to write complex scripts
Cross-Platform Support
Supports x86_64 architecture, suitable for various servers and cloud platforms
Data Persistence
Supports Volume mounting, secure and reliable data, no data loss on container restart
Auto Updates
Supports watchtower for automatic updates, easily get the latest version
Production Ready
Designed for production environments, supports high availability and horizontal scaling
Docker Compose Builder
The simplest and recommended container deployment method
Visual Configuration
Configure all parameters through a friendly Web interface, no need to manually edit YAML files
One-Click Configuration Generation
Automatically generate complete docker-compose.yml files with best practice configurations
Fast Deployment
One-click download configuration files and start services, complete deployment in minutes
Secure and Reliable
Built-in security best practices, automatically configures data volumes and restart policies
Image Source Selection
Choose the most suitable image source based on your network environment and location
Docker Hub
The world's largest container image registry, suitable for international network users
newbe36524/hagicode:0 Azure ACR
Microsoft Azure's image service, faster access from China
hagicode.azurecr.io/hagicode:0 Aliyun ACR
Aliyun's domestic image acceleration, recommended for users in mainland China
registry.cn-hangzhou.aliyuncs.com/hagicode/hagicode:0 FAQ
What's the difference between Container and Desktop versions?
Both versions have their advantages. You can choose based on your usage scenario:
Desktop Version
- Runs locally on your computer, more lightweight
- No server configuration needed, ready to use out of the box
- Suitable for individual developers and light usage scenarios
- All data completely localized
Container Version
- Can be deployed on servers, supports remote access
- Environment isolation, doesn't affect system environment
- Better suited for team collaboration and production environments
- Supports automated deployment and horizontal scaling
What is Docker Compose Builder?
Docker Compose Builder is our visual configuration tool that helps you:
- Configure all container parameters through a Web interface
- Automatically generate docker-compose.yml files
- Built-in best practices and security configurations
- One-click download and start services
No need to manually write complex YAML configurations. Even Docker beginners can deploy easily.
Which system architectures does the container version support?
Hagicode container images currently support x86_64 (amd64) architecture, suitable for most servers and PCs.
Docker will automatically select the appropriate architecture for your system when pulling images.
How to update the container?
When using Docker Compose deployment, updating is very simple:
docker-compose pull
docker-compose up -dOr use Watchtower for automatic updates.
How to configure data persistence?
Docker Compose Builder automatically configures data volumes. By default, your data will be stored in Docker Volumes, ensuring:
- Data is not lost when containers are deleted
- Data is preserved during container upgrades
- Easy backup and recovery
What to do if container startup fails?
Steps to troubleshoot container startup failure:
- Check container status:
docker-compose ps - Check container logs:
docker-compose logs hagicode - Check port occupancy:
If your service port is 3000, use this command to check:
netstat -tlnp | grep 3000If the port is occupied, you can:
- Stop the process occupying the port
- Or configure a different port in Docker Compose Builder
If the issue persists, please check the detailed documentation or contact technical support.
Start Using Docker Compose Builder
The simplest and recommended container deployment method