You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (Jira)" <ji...@apache.org> on 2022/04/29 11:02:00 UTC
[jira] [Comment Edited] (GUACAMOLE-1591) Missing ARM64 PhantomJS
[ https://issues.apache.org/jira/browse/GUACAMOLE-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529907#comment-17529907 ]
Nick Couchman edited comment on GUACAMOLE-1591 at 4/29/22 11:01 AM:
--------------------------------------------------------------------
I ran into the same issue when attempting to build the images on an AWS EC2 T4g instance. This issue is not that we do not include ARM binaries for PhantomJS - we don't include any binaries for PhantomJS. A quick glance at the PhantomJS website indicates that they only provide binaries for x86 platforms, so it's the only thing that Maven can go grab when it goes to do unit testing.
That said, there are three ways you can get around this:
1. Use the pre-built binaries from the web site. Obviously this only works if you're not evaluating something from the git repo or f you don't need the RADIUS extension.
2. Build on an x86-based system and then copy the WAR and JAR files over to your ARM-based system. Since it's Java-based, they will work cross-platform.
3. Comment out the unit testing section of the guacamole-common-js/pom.xml file altogether, which will disable the tests, including PhantomJS.
was (Author: nick.couchman@yahoo.com):
I ran into the same issue when attempting to build the images on an AWS EC2 T4g instance. This issue is not that we do not include ARM binaries for PhantomJS - we don't include any binaries for PhantomJS. The issue is either that PhantomJS only provides x86 binaries, or that we need to do something to download a different architecture - I'm not really sure which one.
That said, there are three ways you can get around this:
1. Use the pre-built binaries from the web site. Obviously this only works if you're not evaluating something from the git repo or f you don't need the RADIUS extension.
2. Build on an x86-based system and then copy the WAR and JAR files over to your ARM-based system. Since it's Java-based, they will work cross-platform.
3. Comment out the unit testing section of the guacamole-common-js/pom.xml file altogether, which will disable the tests, including PhantomJS.
> Missing ARM64 PhantomJS
> -----------------------
>
> Key: GUACAMOLE-1591
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1591
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
> Affects Versions: 1.4.0
> Environment: Client: Docker Engine - Community
> Version: 20.10.14
> API version: 1.41
> Go version: go1.16.15
> Git commit: a224086
> Built: Thu Mar 24 01:47:32 2022
> OS/Arch: linux/arm64
> Context: default
> Experimental: true
> Server: Docker Engine - Community
> Engine:
> Version: 20.10.14
> API version: 1.41 (minimum version 1.12)
> Go version: go1.16.15
> Git commit: 87a90dc
> Built: Thu Mar 24 01:45:52 2022
> OS/Arch: linux/arm64
> Experimental: false
> containerd:
> Version: 1.5.11
> GitCommit: 3df54a852345ae127d1fa3092b95168e4a88e2f8
> runc:
> Version: 1.0.3
> GitCommit: v1.0.3-0-gf46b6ba
> docker-init:
> Version: 0.19.0
> GitCommit: de40ad0
> Reporter: Dedy Martadinata
> Priority: Minor
>
> Building guacamole-client on ARM64 failed due missing binaries of phantomjs for arm64. Building by cloned git repo and use docker build command.
>
> {code:java}
> Downloaded from central: https://repo.maven.apache.org/maven2/com/github/klieber/phantomjs/2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2 (23 MB at 6.3 MB/s)
> #13 391.8 [INFO] Resolved artifact /root/.m2/repository/com/github/klieber/phantomjs/2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2 from central (https://repo.maven.apache.org/maven2, default, releases)
> #13 392.7 [INFO] Extracting /root/.m2/repository/com/github/klieber/phantomjs/2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2/phantomjs-2.1.1-linux-x86_64/bin/phantomjs to /tmp/***-docker-BUILD/target/phantomjs/phantomjs-2.1.1-linux-x86_64/bin/phantomjs
> #13 419.6 Apr 29, 2022 3:01:24 AM org.openqa.selenium.phantomjs.PhantomJSDriverService <init>
> #13 419.6 INFO: executable: /tmp/***-docker-BUILD/target/phantomjs/phantomjs-2.1.1-linux-x86_64/bin/phantomjs
> #13 419.6 Apr 29, 2022 3:01:24 AM org.openqa.selenium.phantomjs.PhantomJSDriverService <init>
> #13 419.6 INFO: port: 3210
> #13 419.6 Apr 29, 2022 3:01:24 AM org.openqa.selenium.phantomjs.PhantomJSDriverService <init>
> #13 419.6 INFO: arguments: [--webdriver=3210, --webdriver-logfile=/tmp/***-docker-BUILD/phantomjsdriver.log]
> #13 419.7 Apr 29, 2022 3:01:24 AM org.openqa.selenium.phantomjs.PhantomJSDriverService <init>
> #13 419.7 INFO: environment: {}
> #13 441.0 Apr 29, 2022 3:01:45 AM org.openqa.selenium.os.UnixProcess checkForError
> #13 441.0 SEVERE: org.apache.commons.exec.ExecuteException: Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "/tmp/***-docker-BUILD/target/phantomjs/phantomjs-2.1.1-linux-x86_64/bin/phantomjs" (in directory "."): error=2, No such file or directory) {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)