You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After step 6, docker-compose up -d you receive the following warnings.
[+] Running 9/9
✔ Network f5-journeys_default Created 0.0s
✔ Container f5-journeys-acc-api-1 Started 0.3s
✔ Container f5-journeys-postgres-1 Started 0.3s
✔ Container f5-journeys-redis-1 Started 0.3s
! acc-api The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s
✔ Container f5-journeys-journeys-1 Started 0.4s
! journeys The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s
✔ Container f5-journeys-celery-worker-1 Started 0.6s
! celery-worker The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s
This references issues: #99
3. Access the web interface and attempt to upload a recent copy of the UCS file using either option, and you get the following error: This references #115.
Expected behavior
It would be expected that no warnings would appear and a UCS file would upload. However, based on previous reports, it appears that the code is hard-locked to a specific platform and using the linux/arm64/v8m (Apple Silicon M2) will not work. There are numerous other issues with vulnerabilities (CVEs) in many of the included packages, so those should also be addresses as well.
Per #99; attempting to use platform: linux/amd64/v8 inside the docker-compose.yml will result in the following error when executing the docker-compose up -d command: image with reference f5devcentral/f5-bigip-journeys-app:v3.3.5 was found but does not match the specified platform: wanted linux/amd64/v8, actual: linux/amd64
If you remove the '/v8" (Apple Silicon specific); it will compose and come up (with no warnings), but will fail exactly like issue #115 when attempting to upload a UCS file.
hi Greg,
speaking with other coworkers here at F5 and digging deeper into it, they believe it won't be supported anytime soon I am afraid.. some of the components used on Journeys already support "the new architecture" however Journeys itself doesn't as you can see documented in our supported architectures below:
Thanks for your comments, we're working on an update for 17.1 support that should be out soon and later we'll add other required fixes and improvements.
Describe the bug
This bug roles together the following issues: #115 and #99.
To Reproduce
Steps to reproduce the behavior:
docker-compose up -d
you receive the following warnings.This references issues: #99

3. Access the web interface and attempt to upload a recent copy of the UCS file using either option, and you get the following error:
This references #115.
Expected behavior
It would be expected that no warnings would appear and a UCS file would upload. However, based on previous reports, it appears that the code is hard-locked to a specific platform and using the linux/arm64/v8m (Apple Silicon M2) will not work. There are numerous other issues with vulnerabilities (CVEs) in many of the included packages, so those should also be addresses as well.
Screenshots

Context
The text was updated successfully, but these errors were encountered: