Is your feature request related to a problem? Please describe.
Scanopy’s Docker container currently requires --network=host to function correctly. When the container is attached to one or more Docker MACVLAN networks, the Scanopy interface does not detect or enumerate those interfaces, despite the container having active MACVLAN-backed network adapters. This prevents deployment in environments where host networking is restricted or where multi-subnet visibility is required.

Describe the solution you'd like
Modify Scanopy’s Docker container and interface enumeration logic to fully support MACVLAN interfaces. Specifically, update any network interface filtering to include MACVLAN adapter types so that all attached MACVLAN interfaces are detected, enumerated, and used for scanning. This would allow Scanopy to operate across multiple subnets while maintaining correct hostname, MAC address, and L2/L3 visibility, functionally equivalent to host networking.

Describe alternatives you've considered

• Continued use of Docker host networking, which is not viable in many security-conscious or multi-tenant environments.
• Running Scanopy directly on the host, which reduces portability and complicates deployment and lifecycle management.
• Deploying multiple containers per subnet, which increases operational overhead and fragments visibility.

Additional context
MACVLAN networking is widely used in production Docker deployments to provide first-class network presence while avoiding host network exposure. Supporting MACVLAN adapters appears to require only a minor code change (likely adapter-type filtering during interface discovery) but would significantly expand Scanopy’s deployment flexibility and network visibility.