Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't build Kissbff image with Docker-compose #970

Open
PTU44 opened this issue Nov 28, 2024 · 1 comment
Open

Can't build Kissbff image with Docker-compose #970

PTU44 opened this issue Nov 28, 2024 · 1 comment

Comments

@PTU44
Copy link

PTU44 commented Nov 28, 2024

Describe the bug
Hi, I downloaded the latest version of Kiss frontend, but when I attempt to create an image,"the application does not respond, and no image is produced"]. This issue didn't exist with the previous version, where everything functioned as expected.

Hoi, Ik kan met de laatste versie geen build image meer maken met docker-compose.
Met een oudere versie van kissbff lukt het zonder problemen. mis ik iets?

Alvast bedankt.

Thanks.

To Reproduce
Steps to reproduce the behavior:
Download latest version of KISS frontend
Install Docker Desktop
use docker-compose build

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows

Error:

it will be ignored, please remove it to avoid potential confusion"
[+] Building 1.7s (16/31) docker:desktop-linux
=> [kiss.bff internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.90kB 0.0s
=> [kiss.bff internal] load metadata for docker.io/library/node:18-alpine 1.0s
=> [kiss.bff internal] load metadata for mcr.microsoft.com/dotnet/aspnet:8.0 0.5s
=> [kiss.bff internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0 0.5s
=> [kiss.bff internal] load .dockerignore 0.0s
=> => transferring context: 426B 0.0s
=> [kiss.bff dotnetbuild 1/8] FROM mcr.microsoft.com/dotnet/sdk:8.0@sha256:f91f9181d68b5ed2c8dea199dbbd2f6d172e60bdc43f8 0.5s
=> => resolve mcr.microsoft.com/dotnet/sdk:8.0@sha256:f91f9181d68b5ed2c8dea199dbbd2f6d172e60bdc43f8a67878b1ad140cf8d6b 0.0s
=> [kiss.bff base 1/4] FROM mcr.microsoft.com/dotnet/aspnet:8.0@sha256:d53ebf3481ea8ac8e4fa5c4213ae1f32a33e68e5b8181868e 0.5s
=> => resolve mcr.microsoft.com/dotnet/aspnet:8.0@sha256:d53ebf3481ea8ac8e4fa5c4213ae1f32a33e68e5b8181868edb11d0496a0043 0.0s
=> => sha256:97efba095bc4c681a00bdbc3dc8816dcf7d7463f78bf1b848c8888137e0060a2 155B / 155B 0.1s
=> => sha256:afefd14b818981ada4866e6245313896fadacbb7be04cb8e149a59f7aa03dfb7 0B / 11.07MB 0.3s
=> => sha256:e0ac362688d16aea6ee8ef565258f85e7176a9a982c108beba740bef2b77a44e 0B / 32.24MB 0.2s
=> => sha256:5703d2113d74e2c9a75b279dd067d32cf650a57c141e87b09b24ce1169be3b23 0B / 18.72MB 0.2s
=> => sha256:a2ab5f4fa232cfe6b6907bf985a58d46f057f0af8262fc70baf7c2942b46c7a0 0B / 3.28kB 0.2s
=> [kiss.bff internal] load build context 0.4s
=> => transferring context: 5.27MB 0.4s
=> [kiss.bff frontend 1/5] FROM docker.io/library/node:18-alpine@sha256:7e43a2d633d91e8655a6c0f45d2ed987aa4930f0792f6d9d 0.0s
=> => resolve docker.io/library/node:18-alpine@sha256:7e43a2d633d91e8655a6c0f45d2ed987aa4930f0792f6d9dd3bffc7496e44882 0.0s
=> CACHED [kiss.bff frontend 2/5] WORKDIR /app 0.0s
=> CANCELED [kiss.bff dotnetbuild 2/8] WORKDIR /src 0.0s
=> CACHED [kiss.bff dotnetbuild 3/8] COPY [Kiss.Bff/Kiss.Bff.csproj, Kiss.Bff/] 0.0s
=> CACHED [kiss.bff dotnetbuild 4/8] RUN dotnet restore "Kiss.Bff/Kiss.Bff.csproj" 0.0s
=> ERROR [kiss.bff dotnetbuild 5/8] COPY .git .git 0.0s
=> CANCELED [kiss.bff frontend 3/5] COPY package*.json . 0.0s
=> CANCELED [kiss.bff base 2/4] WORKDIR /app 0.0s

[kiss.bff dotnetbuild 5/8] COPY .git .git:


failed to solve: failed to compute cache key: failed to calculate checksum of ref 69e8nlrmexvp2nwzhc9db7382::avdps4o9lug185jgw8l6xa12e: "/.git": not found

@PascalIcatt
Copy link
Contributor

Beste @PTU44
Het lijkt er op dat dit keer de code via een zip is gedownload, daardoor mist nu de .git folder in de root map.
We gaan deze afhankelijkheid in een latere release verwijderen.
Als oplossing voor nu kun je de .git directory met de hand toevoegen, of de main branche mbv git updaten.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants