This release is a pre-release and may not be stable for production use.
Manta Node Python
Overview
Distributed edge execution agent for the Manta platform. Manages containerized task execution on compute nodes and provides local services to running tasks.
Quick Start
# Install
pip install -e ".[all]"
# Run node
python -m manta_node --manager-host localhost --manager-port 50051 --token <jwt_token>
# Run multiple nodes
python -c "from manta_node import start_nodes; import asyncio; asyncio.run(start_nodes(3, 'localhost', 50051, '<jwt_token>'))"
Dependency pinning
A released manta-node wheel pins manta-common-core to the exact build the
release was tested with, so installing any manta-node version gives the same
manta-common-core wherever and whenever it is installed. The source
pyproject.toml keeps a range for development and version bumps; only the
published wheel carries the exact pin.
This is stricter than a range: installing manta-node beside a package that
requires a different manta-common-core (for example manta-sdk in one
virtualenv) can fail to resolve. Production nodes run alone in their own
version directory, so this affects only mixed local environments. It fails
loudly at install time, not silently at run time.
Documentation
📚 Full documentation is available at docs.manta-tech.io
For developers working on this component:
- Node Architecture - Container orchestration, service implementation (lives in
mantatech/manta-deploy, where manta-deploy#256 placed it; no accepted ADR decides that placement) - CLAUDE.md - Development guidelines
Architecture
- Container Management: Docker-based task execution
- gRPC Services: LocalServicer and WorldServicer for task communication
- MQTT Integration: Asynchronous command reception
- Resource Monitoring: Real-time metrics collection
Testing
python -m pytest tests/ --cov=manta_node
Docker Setup
For Linux users encountering permission issues:
# Follow Docker post-installation steps
# https://docs.docker.com/engine/install/linux-postinstall/
sudo usermod -aG docker $USER
License
GNU Affero General Public License
1 maintainer
Metadata
1 maintainer
Release files for manta-node 0.6b5.dev806
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| manta_node-0.6b5.dev806-py3-none-any.whl | Python 3 | none | any | Details |
Release files / manta_node-0.6b5.dev806-py3-none-any.whl
| Download URL | manta_node-0.6b5.dev806-py3-none-any.whl |
|---|---|
| Size | 189.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6839e7be1a317821c4543991e10915e4b136cceca0777ec63e024c8802577197
|
|
BLAKE2b-256 checksum How to use checksums |
71af15c532ec562c521308e604b29c57fd7066c4ab0b3f74af5112efe72b36b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for manta-node 0.6b5.dev806
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for manta_node-0.6b5.dev806-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
