celeste-zeng opened a new issue, #28035:
URL: https://github.com/apache/beam/issues/28035

   ### What happened?
   
   Used a multi-arch Beam SDK Python 3.11 container to run a Dataflow pipeline 
on ARM and the container failed to start due to the error `OSError: Could not 
find lib geos_c or load any of its variants ['libgeos_c.so.1', 'libgeos_c.so']. 
`
   
   Reproduce steps: 
   
   1. Create an ARM VM with docker installed;
   2. Pull and run the multi-arch Beam SDK Python 3.11 container: `docker run 
-it --entrypoint=/bin/bash 
gcr.io/dataflow-build/siyuez/mock-release/beam_python3.11_sdk:release-test`;
   3. Use the python interpreter, run: `python`;
   4.  then run: `from apache_beam.io.gcp import bigquery_schema_tools`.
   The error will appear: `File 
"/usr/local/lib/python3.11/site-packages/shapely/geos.py", line 54, in load_dll
       raise OSError(
   OSError: Could not find lib geos_c or load any of its variants 
['libgeos_c.so.1', 'libgeos_c.so'].`
   
   On the VM, the error can be fixed by installing the libgeos-dev package: run 
`apt update` and then`apt install libgeos-dev`. The package takes 4327 kB. We 
should install it in the Dockerfile for Python 3.11 when the target 
architecture is ARM.
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [X] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to