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

Docker build fail #6578

Closed
serzhor opened this issue Oct 30, 2024 · 3 comments
Closed

Docker build fail #6578

serzhor opened this issue Oct 30, 2024 · 3 comments

Comments

@serzhor
Copy link

serzhor commented Oct 30, 2024

Describe the bug
It fails when I run
docker build -f ./Dockerfile -t my-registry/label-studio:test .

[+] Building 243.2s (3/3) FINISHED                                                                                                                                                                                  
 => [internal] load build definition from Dockerfile                                                                                                                                                           0.1s
 => => transferring dockerfile: 32B                                                                                                                                                                            0.0s
 => [internal] load .dockerignore                                                                                                                                                                              0.1s
 => => transferring context: 35B                                                                                                                                                                               0.0s
 => ERROR resolve image config for docker.io/docker/dockerfile:1                                                                                                                                             243.1s
------
 > resolve image config for docker.io/docker/dockerfile:1:
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: unexpected status code [manifests 1]: 504 Gateway Time-out

To Reproduce
Steps to reproduce the behavior:
git clone rhis repo
run docker build

Expected behavior
docker build must create docker image

Screenshots
Screenshot from Readme:
image

Additional context
If I run it with kaniko I also get errors and build fails

INFO[0448] Running: [/bin/sh -c yarn run build && yarn version:libs] 
yarn run v1.22.19
$ NODE_ENV=production yarn ls:build
$ nx run labelstudio:build:production
> nx run labelstudio:build:production
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Entrypoint main [big] 1.46 MiB (7.24 MiB) = runtime.js 6 KiB vendor.js 261 KiB main.css 94.9 KiB main.js 1.11 MiB 40 auxiliary assets
chunk (runtime: runtime) 82.css, 82.js 3.79 MiB (javascript) 6.21 MiB (css/mini-extract) [rendered]
chunk (runtime: runtime) 99.js 3.17 KiB [rendered]
chunk (runtime: runtime) runtime.js (runtime) 14.7 KiB [entry] [rendered]
chunk (runtime: runtime) 492.js (id hint: defaultVendors) 583 KiB [rendered] split chunk (cache group: defaultVendors)
chunk (runtime: runtime) vendor.js (vendor) (id hint: commonVendor) 631 KiB [initial] [rendered] split chunk (cache group: commonVendor) (name: vendor)
chunk (runtime: runtime) 531.css, 531.js (id hint: defaultVendors) 2.27 MiB (javascript) 23.5 KiB (css/mini-extract) [rendered] split chunk (cache group: defaultVendors)
chunk (runtime: 2e845e9bf867bded) 559.js 3.77 KiB [entry] [rendered]
chunk (runtime: runtime) 637.js (id hint: defaultVendors) 3.82 MiB [rendered] split chunk (cache group: defaultVendors)
chunk (runtime: runtime) main.css, main.js (main) 4.42 MiB (javascript) 100 KiB (css/mini-extract) [initial] [rendered]
chunk (runtime: runtime) 814.css, 814.js 1.01 MiB (javascript) 55 KiB (css/mini-extract) [rendered]
WARNING in 82.css
82.css from Css Minimizer plugin
postcss-svgo:: Invalid character in tag name
> 1 | <svgwidth='9'height='5'viewBox='0095'fill='none'xmlns='http://www.w3.org/2000/sv…
    |          ^
  2 | 
 webpack://./node_modules/antd/dist/antd.css:1:0
webpack compiled with 1 warning (c13db131ede19d79)
 
 >  NX   Successfully ran target build for project labelstudio
Done in [141](https://gitlab.corp.geoscan.aero/soft/cv/label-studio/-/jobs/488033#L141).62s.
yarn run v1.22.19
$ nx run-many --target=version
 >  NX   Running target version for 3 projects:
    - datamanager
    - labelstudio
    - editor
 
> nx run editor:version
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "fatal: not a git repository (or any of the parent directories): .git
".] {
  code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v18.20.4
Warning: run-commands command "node ../../tools/version/version.mjs" exited with non-zero status code
> nx run datamanager:version
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "fatal: not a git repository (or any of the parent directories): .git
".] {
  code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v18.20.4
Warning: run-commands command "node ../../tools/version/version.mjs" exited with non-zero status code
> nx run labelstudio:version
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "fatal: not a git repository (or any of the parent directories): .git
".] {
  code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v18.20.4
Warning: run-commands command "node ../../tools/version/version.mjs" exited with non-zero status code
 
 >  NX   Running target version for 3 projects failed
   Failed tasks:
   
   - editor:version
   - datamanager:version
   - labelstudio:version
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1
Cleaning up project directory and file based variables
00:00
ERROR: Job failed: exit code 1
@heidi-humansignal
Copy link
Collaborator

Hello,

I think the build is failing because the docker command doesn't seems correct. Would you mind trying this one:
docker build -t label-studio:latest . within the repo and that should start building the docker image.

Thank you,
Abu

Comment by Abubakar Saad
Workflow Run

@serzhor
Copy link
Author

serzhor commented Oct 31, 2024

I run it at WSLv2 Centos7
Don't know the root cause of the issues, but when I tried to build it at VM in cloud with Ubuntu22 it finished successfully

@serzhor serzhor closed this as completed Oct 31, 2024
@heidi-humansignal
Copy link
Collaborator

It might be with Centos issue with docker setup. I don't think its issue with building. Have you tried building any other image with docker on Centos?

Thank you,
Abu

Comment by Abubakar Saad
Workflow Run

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

No branches or pull requests

2 participants