Feature Request: Support Containerized Deployment of EasyEngine CLI

[dinhngocdung]

Context

Currently, EasyEngine is primarily designed to be installed natively on a host machine. However, there is an increasing demand for running the EasyEngine CLI within a Docker container (a containerized tool) to achieve better environment isolation, portability, and easier cleanup.

The Requirement

When running EasyEngine inside a container, users typically bind-mount the host's /etc/hosts to the container so that EE can manage local domain resolution. To make this work seamlessly, the internal file-handling logic needs to be compatible with Docker's mount mechanisms.

Current Limitation

The current implementation uses atomic file replacement (e.g., Filesystem::dumpFile or creating temporary files and renaming them).

• The issue: Docker prohibits renaming or replacing files that are bind-mounted from the host (like /etc/hosts) because it would change the file's Inode, which Docker uses to maintain the link.
• The result: Users encounter "Device or resource busy" or "Permission denied" errors even when running as root.

Proposed Enhancement

I propose updating the /etc/hosts management functions to use direct stream writing (file_put_contents with LOCK_EX) instead of atomic replacement.

Benefits:

1. Docker Compatibility: Writing directly to the file preserves the Inode, allowing EasyEngine to work perfectly inside a container.
2. Zero Impact on Native Users: This change is transparent and does not affect the existing native installation workflow.
3. Modern Deployment: This officially opens the door for a "Containerized EasyEngine" setup.

Proof of Concept

I have already implemented and tested this solution in a production-ready Docker image: [dinhngocdung/easyengine](https://hub.docker.com/r/dinhngocdung/easyengine). It has been proven to work reliably without side effects.

I have also submitted a draft PR with the specific code changes here: [Link to your PR #476]

Conclusion

By making this minor adjustment to how system files are edited, we can significantly expand the deployment options for EasyEngine without changing its core architecture.

[mrrobot47]

I will check on this in this/coming week and then update here.