Supra CLI Network Connectivity Issue

[alexisad]

Supra CLI Network Connectivity Issue - GitHub Issue Report

Title

CLI deployment fails with "No such device or address (os error 6)" on macOS with containers

Description

Problem Summary:
The Supra CLI successfully compiles Move contracts but fails during deployment with a network connectivity error, preventing actual transaction submission to the testnet.

Environment:

• OS: macOS (Apple Silicon)
• Container: Podman with x86_64 emulation (--platform linux/amd64)
• CLI Version: Latest from Docker Hub (entropy/supra-cli)
• Network: Supra testnet (https://rpc-testnet.supra.com)

Error Details:

Error: No such device or address (os error 6)

Steps to Reproduce:

1. Set up Supra CLI in container with x86_64 emulation
2. Create Move.toml with SupraFramework dependencies
3. Compile contracts successfully with supra move compile
4. Attempt deployment with supra move publish --named-addresses geo_oracle=0xd13b558e67acc2069a1bb417217cf091a09a2ab7d7df9e83fc8352b9c2b3515d

Expected Behavior:
Deployment should submit transaction to testnet and deduct SUPRA tokens from account

Actual Behavior:

• Compilation succeeds (package size 7604 bytes)
• CLI reports successful deployment
• No network transaction is actually submitted
• No SUPRA tokens are deducted from account
• Error occurs during network communication

Additional Context:

• Account has sufficient balance (10 SUPRA)
• Private key and addresses are correctly configured
• Manual RPC attempts also failed due to API format requirements
• Similar containerized CLI tools work fine in same environment

Potential Causes:

• Container networking issue with CLI's network stack
• DNS resolution problems within container
• Firewall/proxy interference (Zscaler was tested but not the issue)
• CLI expecting specific network interface that's not available in container

Request:
Please investigate CLI network connectivity within containerized environments, specifically on macOS with x86_64 emulation. This appears to be an infrastructure issue rather than user configuration error.