Add Docker backend support for MicroPython execution without hardware #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements Docker backend support for micropython-magic, allowing users to run MicroPython code in Docker containers instead of requiring physical MCU hardware.
Key Changes
🐳 Docker Backend Implementation
DockerMicroPython
class that interfaces withmicropython/unix:latest
Docker containersMPRemote2
to support both serial and Docker backends via abackend
parameter--backend docker
and--docker-image
options🎯 Usage Examples
Basic Docker execution:
Line magic with system info:
Custom Docker image:
🔧 Backend Selection
--backend serial
(default, existing behavior) and--backend docker
📚 Documentation & Testing
samples/docker_backend_demo.ipynb
) showcasing all features🎯 Benefits
🚧 Limitations
machine
module functionality)The Docker backend uses the official
micropython/unix:latest
image and is ideal for algorithm development, code validation, and educational use cases before deploying to physical hardware.Fixes #54.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.