-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Beam errors out when using PortableRunner (Flink Runner) – Cannot run program "docker"
#30663
Comments
Cannot run program "docker"
Cannot run program "docker"
Facing same problem. Does anyone has solution? I'm trying to run a basic Kafka pipeline on my M1 MacBook. This is the docker-compose which I'm running as an environment.
and I run a beam_flink1.18_job_server seperatly by docker command.
and this is my Beam pipeline
finally, I'll execute the pipeline by running command on MacBook
and I receive same error in beam_flink1.18_job_server container
|
I think the flink cluster should have the docker installed since it needs to download the Python SDK worker image. |
What happened?
I am trying to deploy a Beam job (Python Beam) that runs on a PortableRunner (Flink Runner) in my Kubernetes cluster.
I have not experienced issues prior with Beam using the Flink Runner. However, today I tried to set up Beam to be a consumer from Apache Kafka using
ReadFromKafka
fromapache_beam.io.kafka
.My Flink Cluster is managed by the Apache Flink Kubernetes Operator.
My Beam jobs are managed by a Beam Flink Job Manager, which posts Beam jobs to the Flink master. The Job Manager uses the image
apache/beam_flink1.16_job_server:2.54.0
.My Flink Task Managers each contain a sidecar for a Beam worker pool, which is spun up using the image
apache/beam_python3.11_sdk:2.54.0
and the arg--worker_pool
.When I start my beam job, I get the following error on the job manager logs:
These are my Beam pipeline options:
Some resources I've found suggest that the Kafka transform has its own environment type which is set to (and overrides any environment you set?)
--environment_type=DOCKER
, which is what causes the issues. However, I could be wrong, so please say so if I am.All of this taking place on a Kubernetes cluster, where, to my knowledge, Docker in Docker is not recommended. I do not want to use a PROCESS environment_type, I require EXTERNAL. How can I resolve this issue? Is this a bug with Beam?
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: