search

INTO-CPS-Association / DTaaS

:factory: :left_right_arrow: :busts_in_silhouette: Digital Twin as a Service
https://into-cps-association.github.io/DTaaS/
Other
116 stars 57 forks source link

[BUG] libms internal load build context fails when building docker/compose.dev.yml #1029

Closed atomicgamedeveloper closed 3 weeks ago

atomicgamedeveloper commented 1 month ago

Describe the bug

Running docker compose -f compose.dev.yml build in /docker fails to build with the following error regarding loading the build context for libms.

[+] Building 28.1s (11/26)                                                                                                              docker:desktop-linux
[...]
 => [libms build 1/6] FROM docker.io/library/node:20.10.0-slim@sha256:5c714c3e90f66a2cbfa266b90a4d7adcd63453cd730aa2d13cba84b260bea2e6                  0.0s 
 => ERROR [libms internal] load build context                                                                                                          26.0s 
 => => transferring context: 537.36MB                                                                                                                  25.9s 
[...]
 => CANCELED [client build 4/6] RUN yarn install --immutable --immutable-cache --check-cache                                                           16.8s
------
 > [libms internal] load build context:
------
failed to solve: archive/tar: unknown file mode ?rwxr-xr-x

To Reproduce

Steps to reproduce the behavior:

  1. Go to './docker'
  2. Run docker compose -f compose.dev.yml build
  3. See error

Expected behavior

The compose.dev.yml to be built succesfully.

Screenshots

image

Application Environment

Please provide the following information:

Additional context

Nothing to add.

prasadtalasila commented 3 weeks ago

@atomicgamedeveloper Both @nichlaes and I can't replicate this error. Can you please check your docker installation again? You can also try running in a fresh Ubuntu VM and see the result.

atomicgamedeveloper commented 3 weeks ago

@atomicgamedeveloper Both @nichlaes and I can't replicate this error. Can you please check your docker installation again? You can also try running in a fresh Ubuntu VM and see the result.

Rebuilding from feature/distributed-demo's HEAD worked. Not sure why it happened, but maybe some interaction with my local changes in that folder.

prasadtalasila commented 3 weeks ago

No longer a problem