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

bug: postee ui dockerfile seems broken #564

Open
simar7 opened this issue Jun 2, 2023 · 6 comments · Fixed by #565 · May be fixed by #571
Open

bug: postee ui dockerfile seems broken #564

simar7 opened this issue Jun 2, 2023 · 6 comments · Fixed by #565 · May be fixed by #571
Assignees

Comments

@simar7
Copy link
Member

simar7 commented Jun 2, 2023

Description

Unable to build Postee UI

What did you expect to happen?

No errors

What happened instead?

GOOS=linux docker build -t simar7/postee-ui:local -f Dockerfile.ui .
[+] Building 38.6s (21/30)
 => [internal] load build definition from Dockerfile.ui                          0.0s
 => => transferring dockerfile: 40B                                              0.0s
 => [internal] load .dockerignore                                                0.0s
 => => transferring context: 2B                                                  0.0s
 => [internal] load metadata for docker.io/library/alpine:3.18.0                 0.8s
 => [internal] load metadata for docker.io/library/node:20-alpine3.17            0.8s
 => [internal] load metadata for docker.io/library/golang:1.18-alpine            0.8s
 => [internal] load build context                                                1.7s
 => => transferring context: 4.17MB                                              1.6s
 => CACHED [vuebuilder 1/5] FROM docker.io/library/node:20-alpine3.17@sha256:45  0.0s
 => CACHED [gobuilder 1/5] FROM docker.io/library/golang:1.18-alpine@sha256:77f  0.0s
 => [stage-2  1/14] FROM docker.io/library/alpine:3.18.0@sha256:02bb6f428431fbc  0.0s
 => CACHED [stage-2  2/14] RUN mkdir /uiserver                                   0.0s
 => CACHED [stage-2  3/14] RUN mkdir /uiserver/www                               0.0s
 => CACHED [stage-2  4/14] RUN mkdir /server                                     0.0s
 => CACHED [stage-2  5/14] RUN mkdir /server/database                            0.0s
 => CACHED [stage-2  6/14] RUN mkdir /config                                     0.0s
 => [vuebuilder 2/5] COPY ./ui/frontend /frontend                                4.0s
 => [gobuilder 2/5] COPY . /server                                               4.0s
 => [gobuilder 3/5] WORKDIR /server/ui/backend                                   0.0s
 => [vuebuilder 3/5] WORKDIR /frontend                                           0.0s
 => ERROR [vuebuilder 4/5] RUN yarn install                                     31.3s
 => [gobuilder 4/5] RUN apk add git                                              1.7s
 => CANCELED [gobuilder 5/5] RUN GOOS=linux GOARCH=amd64 go build --ldflags "-  30.4s
------
 > [vuebuilder 4/5] RUN yarn install:
#22 0.594 yarn install v1.22.19
#22 0.730 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
#22 0.737 [1/4] Resolving packages...
#22 1.225 warning Resolution field "glob-parent@5.1.2" is incompatible with requested version "glob-parent@^6.0.1"
#22 1.462 warning Resolution field "ansi-regex@5.0.1" is incompatible with requested version "ansi-regex@^3.0.0"
#22 1.687 [2/4] Fetching packages...
#22 30.45 error @achrinza/node-ipc@9.2.5: The engine "node" is incompatible with this module. Expected version "8 || 9 || 10 || 11 || 12 || 13 || 14 || 15 || 16 || 17 || 18". Got "20.2.0"
#22 30.46 error Found incompatible module.
#22 30.46 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
executor failed running [/bin/sh -c yarn install]: exit code: 1
@simar7
Copy link
Member Author

simar7 commented Jun 2, 2023

hi @DmitriyLewen and/or @AndreyLevchenko - could you look into this? Currently we can't push a new release because of this.

@afdesk
Copy link
Collaborator

afdesk commented Jun 2, 2023

hi @simar7
I've asked for @nikpivkin to take a look at this issue.
@nikpivkin is our teammate.

@afdesk
Copy link
Collaborator

afdesk commented Jun 2, 2023

@simar7 I remembered that I already tried to fix it: #537
but after #551 is appeared again

there is no a simple way to fix it.

but there is a workaround #565

@simar7 should we change UI?
wdyt?

@afdesk afdesk assigned afdesk and unassigned AndreyLevchenko and DmitriyLewen Jun 2, 2023
@simar7
Copy link
Member Author

simar7 commented Jun 2, 2023

@simar7 I remembered that I already tried to fix it: #537 but after #551 is appeared again

there is no a simple way to fix it.

but there is a workaround #565

@simar7 should we change UI? wdyt?

Yeah I think we should change the UI as you said. This dependency update will keep coming up and I believe the dependency the UI has is no longer supported for newer versions of node.

@simar7 simar7 reopened this Jun 6, 2023
@simar7
Copy link
Member Author

simar7 commented Jun 6, 2023

Re opening this to track the UI change as discussed above

@afdesk
Copy link
Collaborator

afdesk commented Jun 7, 2023

I think it's a right decision.
Let's schedule UI updating in a few weeks.

@nikpivkin nikpivkin linked a pull request Jun 7, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants