pubring.kbx not getting copied

[Goldfels]

trafficstars

• VSCode Version: 1.70.1
• Local OS Version: Fedora Workstation 36
• Local chip architecture: x86
• Reproduces in: Remote - Containers

I'm currently developing a custom Docker container based on a custom Yocto image, that we'd like to use for development. I'd like to run VSCode inside this container, so that the application being developed has a mostly consistent execution environment, that's very close to the real OS.

However, VSCode for some reason fails to copy this file (~/.gnupg/pubring.kbx), and only this file.

By manually copying this file into the container, and restarting the IDE twice, the container starts successfully.

[bamurtaugh]

Transferring as this sounds more Remote-Containers specific than focused on a specific dev container template.

@Goldfels is the flow that you see the .kbx file when you open the project locally in VS Code, and then reopening with Remote-Containers results in the file being missed?

[chrmarti]

Please append the log (F1 > Remote-Containers: Show Container Log). Also make sure the container does not already have a pubring.kbx as we do not overwrite existing files.

[Goldfels]

It seems like after one of the updates, this problem has disappeared, and a new one emerged.

Now, the tar.gz file containing the remote server runs into a gzip: unexpected end of file error when the container tries to extract it. It works fine if I copy the file over and do it manually, but every time VSCode gets an update, it tries updating the server, and fails, which is rather annoying.

The Show Container Log option only showed me an empty window, but I uploaded the "remoteContainers" log file. remoteContainers-2022-09-19T13-46-39.762Z.log

[github-actions[bot]]

Hey @chrmarti, this issue might need further attention.

@Goldfels, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[github-actions[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!