[Docker] Unable to launch container for `linux/arm64`

[cgchinmay]

Describe the bug
Built the docker file on linux/arm64 architecture from the master branch
After launching a container, it crashes with following error

Traceback (most recent call last):
  File "/usr/local/bin/proxy", line 5, in <module>
    from proxy import entry_point
ModuleNotFoundError: No module named 'proxy'

To Reproduce
Steps to reproduce the behavior:

1. docker build -t .
2. launch container using the above image
3. check pod logs for above error

Expected behavior
Container should successfully run

[abhinavsingh]

Woopsie!!! Does the docker container from https://hub.docker.com/repository/docker/abhinavsingh/proxy.py works for you? Another user reported a similar issue earlier #566.

I see stable container was release about 10 months ago on 10th Jan, while master branch was last updated about 9 months ago on 3rd Feb. So there are some difference and possibly a broken container (in the master branch) as you found out.

Frankly, we are going to make another release soon. You can also directly try from develop for now. Lemme dig more and see if I can quick fix the master branch.

[cgchinmay]

The container image didn't work for my use case as I am trying to run it on linux/arm64. The image seems to support only linux/amd64. The base image python:3.10-alpine does support arm64 architecture so I tried building the image from the Dockerfile on arm64 machine. The build was successful but got this error while launching the container. So if you can provide some guidance in debugging above error that would be great. Thanks

[abhinavsingh]

The container image didn't work for my use case as I am trying to run it on linux/arm64. The image seems to support only linux/amd64. The base image python:3.10-alpine does support arm64 architecture so I tried building the image from the Dockerfile on arm64 machine. The build was successful but got this error while launching the container. So if you can provide some guidance in debugging above error that would be great. Thanks

Thank you for bringing this to my notice. Let me dig into it and update. Ideally, our Dockerfile should build for all arch. But lemme confirm back on it, possibly send a fix to develop or a workaround.

[abhinavsingh]

I am wondering is it related to this https://www.docker.com/blog/getting-started-with-docker-for-arm-on-linux/. IIUC, some bootstrap steps are required to run docker on linux/arm64 itself? Please correct me if wrong.

Probably we must build it on linux/arm64 and push that too?

[cgchinmay]

https://www.docker.com/blog/getting-started-with-docker-for-arm-on-linux/

Yes, we need to build it on arm64 instance to be able to do that but there be could be some other go dependencies in Dockerfile which are not arm compatible yet. Thats what we need to check

[abhinavsingh]

proxy.py itself has zero-dependency. We ship openssl with container to assist TLS Interception and HTTPS proxy scenario, otherwise not necessary.

ModuleNotFoundError: No module named 'proxy'

This to me looks like a PYTHONPATH issue?

Develop vs Master

BTW does develop works for you?

[cgchinmay]

I tried both, develop and master. got same error. Okay let me check if its Python path issue inside the container. Will get back to you