BCDS-haoran

While I reproduce this on MacOS, I encounter some problems. I am using orbstack which is a lightweight docker implementation. The pyarmor container ip is 192.168.139.149, proxy container ip is...

I found that I can directly access host(macos) from pyarmor docker, however the output is still the same. ifconfig on docker: docker0: flags=4099 mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast...

@jondy Hi, thanks for quick reply. I've already checked the docs and existing issues. However, it seems the situation is still the same. Does that means pyarmor-auth just cannot running...

@jondy the pyarmor-auth is running in macos host machine, and its machine id is stable. The host machine(192.168.139.3) runs docker container(192.168.139.149), they share same network mask as shown in ifconfig...

@jondy Yes I have already set the host.docker.internal to 192.168.139.3 through editing /etc/hosts, and also export the env variable. **on host machine, I ran pyarmor-auth:** pyarmor-auth ./pyarmor-device-regfile-6694.8.zip 2025-11-12 16:08:41,637: work...

Here's the output of traceroute traceroute 192.168.139.3 traceroute to 192.168.139.3 (192.168.139.3), 30 hops max, 60 byte packets 1 192.168.139.3 (192.168.139.3) 0.618 ms 0.259 ms 0.185 ms

after that, the pyarmor gen command run succeed pyarmor gen --enable-rft foo.py INFO Python 3.12.12 INFO Pyarmor 9.1.8 (group), 006694, xxx INFO Platform linux.x86_64 INFO search inputs ... INFO find...