sklibanov312 commented on issue #2829: URL: https://github.com/apache/drill/issues/2829#issuecomment-2084198556
I've worked around this with a custom Dockerfile: ``` FROM debian:12 # We're going to be installing things RUN apt-get update # Here's some basic conveniences, and Java because Drill runs on that RUN apt-get install -y ca-certificates curl net-tools bind9-utils dos2unix less procps expect default-jre # Create a non-root user and switch to it RUN groupadd -r drill RUN useradd --no-log-init -r -g drill -m drill WORKDIR /home/drill COPY ./apache-drill-1.21.1.tar.gz /home/drill COPY ./docker-entrypoint.sh /home/drill RUN chown -R drill:drill /home/drill USER drill RUN tar xvfz apache-drill-1.21.1.tar.gz RUN chmod u+rwx /home/drill/docker-entrypoint.sh # In case your host is Windows... RUN dos2unix /home/drill/docker-entrypoint.sh CMD ["/home/drill/docker-entrypoint.sh"] ``` The docker-entrypoint.sh has this: ``` #!/bin/bash # The 'unbuffer' part is a workaround for https://github.com/apache/drill/issues/2829 unbuffer apache-drill-1.21.1/bin/drill-embedded ``` With port 8047 forwarded I can still talk to it thru the web page. So that's the workaround. Now I can run this in a docker compose stack or whatever, without having to add -ti. -- 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: dev-unsubscr...@drill.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
