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

HELP: How to build arm64 supported OS image for selenoid/firefox and selenoid/chrome #651

Open
aaggarwal-sumo opened this issue Nov 3, 2023 · 6 comments

Comments

@aaggarwal-sumo
Copy link

aaggarwal-sumo commented Nov 3, 2023

Hi Team,

Can anyone please help with steps we need to follow for building arm64 supported OS image for selenoid/firefox and selenoid/chrome. I tried following. the https://github.com/aerokube/images/blob/master/docs/building-images.adoc#building-procedure and I was getting error:

aaggarwal@aaggarwal-mac images % go install github.com/markbates/pkger/cmd/pkger@latest
go: downloading github.com/markbates/pkger v0.17.1
go: downloading github.com/gobuffalo/here v0.6.0
aaggarwal@aaggarwal-mac images % go generate github.com/aerokube/images
go: downloading github.com/spf13/cobra v1.1.1
go: downloading github.com/hashicorp/go-version v1.6.0
go: downloading gopkg.in/cheggaaa/pb.v1 v1.0.28
go: downloading github.com/mattn/go-runewidth v0.0.9
go: downloading golang.org/x/sys v0.0.0-20220712014510-0a85c31ab51e
go: downloading github.com/spf13/pflag v1.0.5
main.go:7: running "pkger": exec: "pkger": executable file not found in $PATH
aaggarwal@aaggarwal-mac images %  go build
aaggarwal@aaggarwal-mac images % ./images chrome -b 118.0.5993.117 -d 118.0.5993.70 -t selenoid/chrome:arm118 
2023/11/03 16:07:41 running command: docker build -t selenoid/dev_chrome:118.0.5993.117 --build-arg VERSION=118.0.5993.117 /var/folders/9f/yrtnqzzx63l9xrtsqg0_hcwm0000gp/T/images4181880619/chrome/apt
[+] Building 2.6s (4/4) FINISHED                                                                                                                                                                                                                     
 => [internal] load build definition from Dockerfile                                                                                                                                                                                            0.0s
 => => transferring dockerfile: 1.14kB                                                                                                                                                                                                          0.0s
 => [internal] load .dockerignore                                                                                                                                                                                                               0.0s
 => => transferring context: 2B                                                                                                                                                                                                                 0.0s
 => ERROR [internal] load metadata for docker.io/library/base_image:latest                                                                                                                                                                      2.5s
 => [auth] library/base_image:pull token for registry-1.docker.io                                                                                                                                                                               0.0s
------
 > [internal] load metadata for docker.io/library/base_image:latest:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
2023/11/03 16:07:44 command error: build dev image: command execution error: exit status 1
@aaggarwal-sumo
Copy link
Author

@vania-pooh and @sskorol Can you please help me here.

@aaggarwal-sumo
Copy link
Author

Can anyone please help me here

@vania-pooh
Copy link
Member

@aaggarwal-sumo we never tried building ARM image for Firefox.

@aaggarwal-sumo
Copy link
Author

Can you share steps for ARM64 for chrome latest version 117 or 118

@aaggarwal-sumo
Copy link
Author

@vania-pooh

I tried creating my self but when I am running test case it is failing in creating the connection:

I am able to run selenoid on 444 and selenoid ui 8080 and it shows connected but When I am triggering test case it fails to create session:

[2023-11-08T08:16:07.438Z] 2023-11-08T08:16:07.438Z ERROR webdriver: Request failed with status 500 due to session not created: no bindings available for 4444/tcp
[0-0] [2023-11-08T08:16:07.441Z] 2023-11-08T08:16:07.438Z ERROR webdriver: session not created: no bindings available for 4444/tcp
[0-0] at getErrorFromResponseBody (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/webdriver/build/utils.js:197:12)
[0-0] at NodeJSRequest._request (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/webdriver/build/request/index.js:166:60)
[0-0] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-0] at async startWebDriverSession (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/webdriver/build/utils.js:67:20)
[0-0] at async Function.newSession (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/webdriver/build/index.js:46:45)
[0-0] at async remote (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/webdriverio/build/index.js:77:22)
[0-0] at async Runner._startSession (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/@wdio/runner/build/index.js:223:56)
[0-0] at async Runner._initSession (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/@wdio/runner/build/index.js:176:25)
[0-0] at async Runner.run (/Users/aaggarwal/Documents/Sumo-Repo/Aman_UI/sumo-ui-test/UIE2ETests/node_modules/@wdio/runner/build/index.js:88:19)
[0-0] [2023-11-08T08:16:07.442Z] 2023-11-08T08:16:07.442Z ERROR @wdio/runner: Error: Failed to create session.

Checked conatiner logs :

selenoid | 2023/11/08 08:16:07 [-] [NEW_REQUEST] [unknown] [192.168.65.1]
selenoid | 2023/11/08 08:16:07 [-] [NEW_REQUEST_ACCEPTED] [unknown] [192.168.65.1]
selenoid | 2023/11/08 08:16:07 [114] [LOCATING_SERVICE] [chrome] [117.0]
selenoid | 2023/11/08 08:16:07 [114] [USING_DOCKER] [chrome] [117.0]
selenoid | 2023/11/08 08:16:07 [114] [CREATING_CONTAINER] [aaggarwalsumologic/chromium:117]
selenoid | 2023/11/08 08:16:07 [114] [STARTING_CONTAINER] [aaggarwalsumologic/chromium:117] [6a8563f524b8529cb90823d9dac68691ea72a1f39a2de7795fca6097bc3b82a8]
selenoid | 2023/11/08 08:16:07 [114] [CONTAINER_STARTED] [aaggarwalsumologic/chromium:117] [6a8563f524b8529cb90823d9dac68691ea72a1f39a2de7795fca6097bc3b82a8] [0.11s]
selenoid | 2023/11/08 08:16:07 [114] [REMOVING_CONTAINER] [6a8563f524b8529cb90823d9dac68691ea72a1f39a2de7795fca6097bc3b82a8]
selenoid | 2023/11/08 08:16:07 [114] [FAILED_TO_REMOVE_CONTAINER] [6a8563f524b8529cb90823d9dac68691ea72a1f39a2de7795fca6097bc3b82a8] [Error response from daemon: No such container: 6a8563f524b8529cb90823d9dac68691ea72a1f39a2de7795fca6097bc3b82a8]
selenoid | 2023/11/08 08:16:07 [114] [SERVICE_STARTUP_FAILED] [no bindings available for 4444/tcp]

@dempc6469
Copy link

@aaggarwal-sumo were you ever able to resolve this?

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

3 participants