stickies-v / vs-core Goto Github PK

Since the goal of this project is to make it quick and easy to have a fully function dev environment, hosting the Docker image on Docker Hub could speed up that process by at least a few minutes. Providing the Dockerfile here would still enable users to build locally if they prefer. Also would remove the Docker Compose dependency.

From the README:

git clone https://github.com/stickies-v/vs-core
cd vs-core/local/
devcontainer open

There is no local/ directory.

On 45c79db install fails at:

Running the postStartCommand from devcontainer.json...

[514247 ms] Start: Run in container: /bin/sh -c /scripts/init.sh
Cloning into 'bitcoin'...
warning: templates not found in /home/harding/.config/git-template
remote: Enumerating objects: 258319, done.
remote: Counting objects: 100% (199/199), done.
remote: Compressing objects: 100% (141/141), done.
remote: Total 258319 (delta 117), reused 98 (delta 56), pack-reused 258120
Receiving objects: 100% (258319/258319), 231.10 MiB | 1.87 MiB/s, done.
Resolving deltas: 100% (185056/185056), done.
Renaming remote references: 100% (7/7), done.
cp: cannot create regular file '/workspace/bitcoin/.git/hooks/pre-push': No such file or directory
[649133 ms] postStartCommand failed with exit code 1. Skipping any further user-provided commands.
Done. Press any key to close the terminal.

Notes:

• It's unclear to me whether it's trying to create /workspace/bitcoin on my host filesystem on the container filesystem. If it's the host system, I certainly don't have a /workspace directory.
• I don't think it's the issue here, but you can see it's trying to access my git templates. The existence of those and other custom git configuration is a potential future source of failures in a command that expects git to behave consistently across systems.

VSCode Dev Containers reported it was unable to connect to docker daemon. It was looking for the socket /var/run/docker.sock but Docker Deskop created it at ~/.docker/desktop/docker.sock . I was able to bypass the issue by symlinking.

System configuration:

Pop-os (Ubuntu derivative)
Docker desktop installed from Docker.com (fresh install)
Previous installation of docker.io from Ubuntu (removed but configuation files were not purged)
VS Code (fresh install)

Related search result found during my debugging: https://youtrack.jetbrains.com/issue/IDEA-294871/Docker-desktop-for-linux-create-docker.sock-in-other-folder-instead-of-var-run-docker.sock