codesandbox / codesandbox/codesandbox-client

Unable to setup dicedb repo with code sandbox

Open
#8,539 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

Cannot setup the diceDB repo with code sandbox

How has this issue affected you? What are you trying to accomplish?

I'm trying to work on the project , dicedb

To Reproduce

Following error occurs

Dockerfile-with-features:11
--------------------
   9 |     COPY . .
  10 |     
  11 | >>> RUN CGO_ENABLED=0 GOOS=linux go build -o /dicedb/dice-server
  12 |     EXPOSE 7379
  13 |     CMD ["/dicedb/dice-server"]
--------------------
ERROR: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=linux go build -o /dicedb/dice-server" did not complete successfully: exit code: 2
Error: Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-pitcher-host/container-features/0.50.2-1723387177954/Dockerfile-with-features -t vsc-dice-549272b079e140288873d022f64f5046a7f639b77120d26e938c604f7932b907 --target dev_containers_target_stage --build-context dev_containers_feature_content_source=/tmp/devcontainercli-pitcher-host/container-features/0.50.2-1723387177954 --build-arg _DEV_CONTAINERS_BASE_IMAGE=dev_container_auto_added_stage_label --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /project/dice
    at IAA (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:463:1698)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async qw (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:462:1691)
    at async mK (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:462:610)
    at async mAA (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:479:3660)
    at async LC (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:479:4775)
    at async jeA (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:611:12219)
    at async _eA (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:611:11960)
{"outcome":"error","message":"Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-pitcher-host/container-features/0.50.2-1723387177954/Dockerfile-with-features -t vsc-dice-549272b079e140288873d022f64f5046a7f639b77120d26e938c604f7932b907 --target dev_containers_target_stage --build-context dev_containers_feature_content_source=/tmp/devcontainercli-pitcher-host/container-features/0.50.2-1723387177954 --build-arg _DEV_CONTAINERS_BASE_IMAGE=dev_container_auto_added_stage_label --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /project/dice","description":"An error occurred building the image."}
Failed to run containers Command failed with exit code 1: devcontainer up --workspace-folder=/project/dice --override-config=/tmp/pitcher-containers/pitcher-host/workdir/.devcontainer.json --remove-existing-container --skip-post-attach --skip-post-create --additional-features="{\"ghcr.io/codesandbox/devcontainer-features/codesandbox:0.1.4\":{}}" --mount=type=bind,source=/project/dice,target=/project/dice --mount=type=bind,source=/project/home/pitcher-host/.persisted,target=/persisted --mount=type=bind,source=/project/home/pitcher-host/.cache,target=/root/.cache --mount=type=bind,source=/project/home/pitcher-host/.docker/run/docker.sock,target=/var/run/docker.sock --mount=type=bind,source=/usr/local/bin/lsp/,target=/usr/local/bin/lsp/ --mount=type=bind,source=/vscode,target=/vscode --mount=type=bind,source=/run/user/1001,target=/var/run --mount=type=bind,source=/pitcher/pitcher/out/pitcher-fs-server/fs-server,target=/usr/local/bin/fs-server --mount=type=bind,source=/opt/git,target=/opt/git --mount=type=bind,source=/opt/git/bin/git,target=/usr/bin/git --mount=type=bind,source=/opt/git/bin/git,target=/usr/local/bin/git
Link to sandbox: link
Your Environment
Software Name/Version
Сodesandbox
Browser Safari
Operating System MacOS

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked CodeSandbox workspace and the Dockerfile-with-features failure at line 11, where the Go build command exits with code 2. Reproduce the setup and inspect the missing build output to identify the cause; done means the diceDB repository builds and its development container starts successfully in CodeSandbox.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
build-system, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.