Any well-known way to deploy sw360 using an official image #2177
Replies: 6 comments 8 replies
-
The name of published image comes from previous repository name change, and is a bug. Thanks for catching up. |
Beta Was this translation helpful? Give feedback.
-
Main package is public now: I will raise the decision over latest on next sw360 meeting. |
Beta Was this translation helpful? Give feedback.
-
Can you try in a local system instead of play-with-docker |
Beta Was this translation helpful? Give feedback.
-
Ok, this is interesting, duplicated libraries ( version wise ) was a problem in the past and that's why we went to the shared approach. |
Beta Was this translation helpful? Give feedback.
-
I will look closely next week. |
Beta Was this translation helpful? Give feedback.
-
@davidecavestro The docker interface is stable now |
Beta Was this translation helpful? Give feedback.
-
I've seen the recommended setup is based on self-building the docker image.
The official compose uses the image ghcr.io/eclipse-sw360/sw360:latest which is not published, but the locally built image has that name.
OTOH there's an image hosted at ghcr.io/eclipse/sw360:latest (please note the name differs).
At the moment locally building the image fails both on main and on the last tag (I can provide details if interested, but doesn't really matter here).
When I adapt the compose to run with the image at ghcr.io/eclipse/sw360:latest I get some errors at spring startup (i.e. IdleConnectionMonitor$CleanupTask rejected, with pool size = 0 or InvokerFilter cannot be found by ... liferay-theme and so on), so before going too much into depth, I'd like to know:
is there any well known way to deploy sw360 using an official image with some predefined config?
Beta Was this translation helpful? Give feedback.
All reactions