Docker Compose Up does not work #29550
Comments
|
Hey @dneville-cvs! I'm here to help you with your Docker Compose issue. I'm Dosu, a bot that can assist you in solving bugs, answering questions, and becoming a contributor. Let's work on resolving this together! To resolve the error encountered when running
Additionally, ensure you are using the correct versions of
This information is found in the following section of the Dockerfile: FROM apache/superset:3.1.0
USER root
RUN apt-get update && \
apt-get install --no-install-recommends -y firefox-esr
ENV GECKODRIVER_VERSION=0.29.0
RUN wget -q https://github.com/mozilla/geckodriver/releases/download/v${GECKODRIVER_VERSION}/geckodriver-v${GECKODRIVER_VERSION}-linux64.tar.gz && \
tar -x geckodriver -zf geckodriver-v${GECKODRIVER_VERSION}-linux64.tar.gz -O > /usr/bin/geckodriver && \
chmod 755 /usr/bin/geckodriver && \
rm geckodriver-v${GECKODRIVER_VERSION}-linux64.tar.gz
RUN pip install --no-cache gevent psycopg2 redis
USER supersetThese steps should help mitigate issues related to building assets within the Docker container, especially on resource-constrained devices like an M2 Macbook Pro [1][2]. |
|
The bot might be right about this being a resource constraing, but I haven't seen if fail at that step before, so I'll also CC/assign our resident Docker guru, @mistercrunch. |
|
@dosu I have followed the recommended steps, but I'm still encountering the error. I ran I also confirmed geckodriver and firefox: However, it was still this error: |
|
The error you're encountering suggests that the downloaded files might be corrupted. This can sometimes happen due to network issues or problems with the source files. Here are a few steps you can try to resolve this:
These steps should help you bypass the issue with corrupted downloads during the Docker build process. If the issue persists, @mistercrunch, our resident Docker expert, might have additional insights. |
|
Well, following @dosu 's advice, I at least got a different error. Docker builder prune, then manually download and verify files and edit the Dockerfile as instructed, and the result is below: |
|
To resolve the issue of the # Install GeckoDriver WebDriver
ARG GECKODRIVER_VERSION=v0.34.0 \
FIREFOX_VERSION=125.0.3
# Add the checksum for the geckodriver version you are downloading
ARG GECKODRIVER_CHECKSUM=your_geckodriver_checksum_here
RUN apt-get update -qq \
&& apt-get install -yqq --no-install-recommends wget bzip2 \
&& wget -q https://github.com/mozilla/geckodriver/releases/download/${GECKODRIVER_VERSION}/geckodriver-${GECKODRIVER_VERSION}-linux64.tar.gz -O geckodriver.tar.gz \
&& echo "${GECKODRIVER_CHECKSUM} geckodriver.tar.gz" | sha256sum -c - \
&& tar xfz geckodriver.tar.gz -C /usr/local/bin \
&& rm geckodriver.tar.gz \
# Install Firefox
&& wget -q https://download-installer.cdn.mozilla.net/pub/firefox/releases/${FIREFOX_VERSION}/linux-x86_64/en-US/firefox-${FIREFOX_VERSION}.tar.bz2 -O firefox.tar.bz2 \
&& tar xfj firefox.tar.bz2 -C /opt \
&& ln -s /opt/firefox/firefox /usr/local/bin/firefox \
&& rm firefox.tar.bz2 \
&& apt-get autoremove -yqq --purge wget bzip2 && rm -rf /var/[log,tmp]/* /tmp/* /var/lib/apt/lists/*Make sure to replace |
|
Are you on Windows/cygwin? In any case, the command that seems to fail is an |
|
@mistercrunch I am on macOS 14.5 (23F79). I created a minimal Dockerfile: I ran this command to build: I got the same results: I'm curious if you get the same error. |
|
ok, here's my true minimum repro: |
|
Maybe a dumb question, but does the host have internet access? Can you |
|
@mistercrunch definitely not a dumb question - I also tested just using wget directly on the terminal and it worked just fine with this command: But also, the wget for geckodriver works just fine in the Docker container, it is only Firefox that fails. |
|
Oh right, and it's pretty clear that its the If you can repro consistently and that's not just a cosmic ray type thing there's probably something in your network stack or local cdn.mozilla.net that's corrupted. Actually that's probably the best explanation, your particular regional instance of the mozilla.cdn has this one file corrupted. For the sake of this issue it could be good to share which region you're in so that we can check this hypothesis. |
|
Ok, I think you are correct about it being something in my network stack... I just tried a vpn instead of my regular network and was unable to repro the issue there. I'll close this issue and open one with the network folks at work. Thanks for your help! |
Bug description
When I run
docker compose upas I'm trying to follow this guide, I get the following error:How to reproduce the bug
docker compose upScreenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
I am on an M2 Macbook Pro. I have made no modifications to the repo. I have made sure I'm on an up-to-date master branch. I have turned all the Docker resource settings to max.
Checklist
The text was updated successfully, but these errors were encountered: