gpg | Geophysics for Practicing Geoscientists

I had not specified this in the original question, but I had used conda to set up a virtual environment. Somehow that doesn't work, so I'd recommend following the tutorial to the letter and use pipenv.

Make sure the content of the /etc/apt/sources.list.d/docker.list corresponds to the output of the command in the documentation, bullet #3.

At the time of this writing executing the command on my Ubuntu 20.04 LTS results in the following content of the docker.list file:

deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu focal stable

which seems to be different from that of yours.

answer found here : https://suay.site/?p=526

in short :

retrieve the key and add the key :

Update: Version 1.6.9 has been released and should fix this issue! 🎉

This is actually a known bug, which is now open for quite a while: OSSRH-66257. There are two known workarounds:

As a workaround, use --add-opens to give the library causing the problem access to the required classes:

Every time you execute docker-compose run you create a new container, so the gems previously installed are not available anymore.

In order to solve your problem you could run bundle install in Dockerfile, install the gems in the app folder bundle install --path vendor/bundle or mount the directory bundle uses by default to store the gems, typically /usr/local/bundle

As @iravinandan said you need to set up a tunnel.

Publishing a port alone won't help as all incoming requests are going through an http proxy.

If you dig CNAME .githubpreview.dev you will see it's github-codespaces.app.online.visualstudio.com. You can put anything in the githubpreview.dev subdomain and it will still be resolved on the DNS level.

The proxy relies on HTTP Host header to route the request to correct upstream so it will work for HTTP protocols only.

To use any other protocol (MongoDb wire protocol in your case) you need to set up a TCP tunnel from codespaces to your machine.

At the time of writing the default Node + Mongo codespace uses Debian buster, so ssh port forwarding would be the obvious choice. In the codespace/VSCode terminal:

Allow me to give credit to they who deserve it!! The correct answer was provided by earlopain in this issue on rails/rails

It's actually an almost embarrassingly easy fix - once you know it :)

Add tty: true to your docker-compose.yml - like this

Great question, but it's not exactly the corporate proxy refusing self-signed certificates; it's pacman's SSL agent.

In your browser, go to repo.msys2.org to find which certificates are being used:

Open details:

You'll need to export all certificates individually, but don't need the lowest one for repo.msys2.org:

Save to a local file:

Export using Base-64 encoding:

Can save directly to the trust source anchors folder. Things move around from time to time, but as of now, that's C:\msys64\etc\pki\ca-trust\source\anchors\.cer

Go through the same steps to import the top-level root certificate. Save in the same path, different file name.

Each user on GitHub can upload their public key to GitHub to be used for verifying commits. Only the keys that the user has uploaded are considered valid for verifying that user's commits.

When a commit comes in, GitHub inspects the email addresses in the author and committer headers of the commit, and it uses that to determine the accounts associated with it. For signatures, only the committer account is considered, since the commit was created by the committer and could only have been validly signed by them. Then, if that user has a public key and the commit is signed, GitHub will use that key to verify it.

When we verify any secure digital signature, we learn one of two things. Either we learn that both the given key signed the message and the message has not been modified, or we learn that something else has occurred. That something else could be a different key signed the message, that the message was modified, or that a bug of some sort occurred, but all we know in that case is that the signature is not valid for that key-message combination.

If Eve tries to sign a commit for Bob, then GitHub will try to verify the signature with Bob's key, and it will fail verification. The commit will be flagged as unverified.