Skip to content

Conversation

@jeremychoi
Copy link
Member

The difference with the existing Containerfile is the kubectl installation URL.

@sfowl
Copy link
Collaborator

sfowl commented Aug 21, 2024

Some other options aside from having a second Containerfile could be:

  • Use a base image like registry.redhat.io/openshift4/ose-cli-rhel9 which includes kubectl
  • Use the output from something like uname -p to create the URL for downloading kubectl

@cedricbu
Copy link
Collaborator

What about Firefox ? does it also require change for ARM ?

@jeremychoi
Copy link
Member Author

Thanks for the suggestions. I updated Containerfile and removed the new file, going for (2). @cedricbu do you happen to know the link for arm64 one?

@cedricbu
Copy link
Collaborator

I was looking after my comment, and actually it doesn't look straight forward:
IIUC, Firefox doesn't release firefox releases for Linux ARM64 (e.g.: https://download-installer.cdn.mozilla.net/pub/firefox/releases/129.0.2/ => only Win ARM64 is present). However, the nightly builds seems to have ARM64 Linux builds : https://download-installer.cdn.mozilla.net/pub/firefox/nightly/2024/08/2024-08-20-21-40-25-mozilla-central/

So I am not sure how to do, but it might be that ARM64 binaries of official releases will come soon.

ZAP is using a Debian base and install Firefox directly using APT. However, this is not possible for us currently (the RHEL UBI doesn't have firefox RPM available, this is why we need to download it manually).

Maybe the short term would be to simply not install Firefox for the ARM image, and find a better solution later ?

@jeremychoi
Copy link
Member Author

hold until firefox arm64 for linux is available to download.

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

Successfully merging this pull request may close these issues.

3 participants