[SERVER-76442] GPG error when trying to initialize mongo 4.2 docker container. Created: 22/Apr/23  Updated: 26/Apr/23  Resolved: 26/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.2.0, 4.2.24
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Emiliano Escobedo Assignee: Yuan Fang
Resolution: Done Votes: 0
Labels: repository
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot from 2023-04-22 03-30-33.png    
Operating System: ALL
Steps To Reproduce:
  1. Create a docker-compose file with mongo 4.2 container in it.
  2. run docker-compose -f "filename" up -d
Participants:

 Description   

When trying to start a docker container for a mongo database in version 4.2, a GPG error is stopping the container to start. (The repository 'http://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.2 Release' is not signed.)



 Comments   
Comment by Yuan Fang [ 26/Apr/23 ]

Hi jeep.escobedo@gmail.com,

Thank you for your report. The error message appears to suggest that the GPG key is missing from your system. I would recommend referring to the official documentation on how to verify the integrity of MongoDB packages for further guidance.

If you have further questions, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

Regards,
Yuan

Generated at Thu Feb 08 06:32:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.