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
{{ message }}
This repository was archived by the owner on Nov 17, 2018. It is now read-only.
Affects: 0.0.480
Issue
We're using the builder-maven image to build our applications and that build uses binaries that only run on a 64-bits OS.
I think that the 32 bits image was a conscious choice on your side (given you specifically use Java 32 bits) probably to slim the images down?
Proposed solution(s)
I'd like to propose a few solutions to fuel the discussion on that topic which from what I gather might have deep impacts if implemented
The first would have a strong impact on all users but there are going to be more and more 64 bits only tools out there so it might be all right.
The second would probably be the heaviest but cleanest of them all with no impacts on current users.
The third would have no impacts on current users and would allow on-demand workload distribution but might not be as clean as the second.
Do you think any of those is possible? Is there another option that I don't see?
Thanks for developing those images anyway, we heavily rely on them and they're pretty useful!