dosubot[bot] commented on issue #30404:
URL: https://github.com/apache/superset/issues/30404#issuecomment-2377364633

   <!-- Greeting -->
   Hello @Iamtheoldman! I'm here to help you with any bugs or questions you 
have. I can also assist you in becoming a contributor while we wait for a human 
maintainer.
   
   <!-- Answer -->
   The issue you're encountering with GPG key errors during the Docker build 
process is due to invalid signatures for the Debian repositories. This is not 
directly related to Superset but rather to the Debian repositories being 
accessed.
   
   To resolve this, you can add the following steps to your Dockerfile to 
update the GPG keys:
   
   ```dockerfile
   FROM debian:bookworm
   
   # Add the necessary GPG keys
   RUN apt-get update -qq && apt-get install -yqq --no-install-recommends \
       gnupg2 \
       && apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
648ACFD622F3D138 \
       && apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
04EE7237B7D453EC \
       && apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
0E98404D386FA1D9 \
       && apt-get update -qq
   
   # Install the required packages
   RUN apt-get install -yqq --no-install-recommends \
       libnss3 \
       libdbus-glib-1-2 \
       libgtk-3-0 \
       libx11-xcb1 \
       libasound2 \
       libxtst6 \
       git \
       pkg-config \
       && rm -rf /var/lib/apt/lists/*
   ```
   
   This will add the necessary GPG keys and should resolve the GPG errors you 
are encountering during the Docker build process.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to