Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update riak build scripts to use a newer Ubuntu image #163

Open
MoralCode opened this issue Apr 23, 2024 · 3 comments
Open

update riak build scripts to use a newer Ubuntu image #163

MoralCode opened this issue Apr 23, 2024 · 3 comments

Comments

@MoralCode
Copy link

Per my comments on #117 this seems like it should be logged as a TODO for anyone who is planning to use this.

The current config uses an ubuntu 18 docker image and a libssl1.0.0 library that isnt available in later version - there may be other issues too, thats just the one that i noticed

@MoralCode MoralCode changed the title update KNIX build scripts to use a newer Ubuntu VM update KNIX build scripts to use a newer Ubuntu image Apr 23, 2024
@MoralCode MoralCode changed the title update KNIX build scripts to use a newer Ubuntu image update riak build scripts to use a newer Ubuntu image Apr 23, 2024
@iakkus
Copy link
Member

iakkus commented Apr 23, 2024

Have you tried checking whether the riak package actually works with the newer Ubuntu image?

@MoralCode
Copy link
Author

MoralCode commented Apr 23, 2024

not yet. Im almost certain it wont (if the only change you make is changing the docker image tag) because the libssl1.0.0 package also needs upgrading (its not available in later ubuntu versions, only newer versions are). I'm also not sure what else might need to be upgraded and i'd like to get myself a little more familiar with the codebase before making a major change like this.

I was largely just filing this issue to document it so that someone can tackle it in the future, especially if I don't get around to trying it this semester.

@MoralCode
Copy link
Author

MoralCode commented Apr 29, 2024

#117 (comment) seems to be cited in the README of the ansible scripts as a workaround for this - may be useful to anyone looking to integrate the fix into the install process itself

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

No branches or pull requests

2 participants