LOCKSS 2.0-alpha4 System Manual
Welcome to the LOCKSS 2.0-alpha4 System Manual.
Security advisories: CVE-2021-44228 ("Log4Shell"), CVE-2021-45046, CVE-2021-4104, CVE-2021-45105, CVE-2021-44832
LOCKSS 2.0-alpha4 and the custom Solr and OpenWayback containers it includes are affected.
See Security Advisories.
Containers are now orchestrated by K3s, a lightweight Kubernetes distribution by Kubernetes vendor Rancher, compatible with most Linux flavors through a convenient multi-OS installer.
Also: numerous bug fixes and enhancements in the repository service; security enhancements (non-root containers, firewalling, authentication, LCAP SSL...), Web user interface enhancements, and more.
See Release Notes for more details.
In order to install and test the LOCKSS 2.0-alpha4 system, you will need a 64-bit Linux host (physical or virtual) with at least 4 CPU cores and 8 GB of memory, and adequate storage; Git (to download the LOCKSS Installer from GitHub); and K3s, a lightweight Kubernetes environment (installed via the LOCKSS Installer).
If you were running LOCKSS 2.0-alpha3, you no longer need MicroK8s or Snap. See Upgrading From LOCKSS 2.0-alpha3 for more details.
Questions and Answers
- I have an existing classic LOCKSS system (version 1.x). Can I upgrade to LOCKSS 2.0-alpha4?
The LOCKSS 2.0-alpha4 release is a technology preview which we are excited to share with the community for testing purposes. It is not yet possible to convert from a classic LOCKSS system (e.g. version 1.75.5) to a LOCKSS 2.0 system. To help us advance toward the final LOCKSS 2.0 release, please consider installing and running the LOCKSS 2.0-alpha4 release on a test machine and providing us with your feedback.
- I have a LOCKSS system running 2.0-alpha3. Can I upgrade to LOCKSS 2.0-alpha4?
Yes. You are welcome to wipe your testing data from LOCKSS 2.0-alpha3 and start from scratch, but there is an upgrade path from LOCKSS 2.0-alpha3.
- Can I use my own PostgreSQL database? Can I use my own Solr database?
Yes, you can configure the system to use your institution's Postgres database and/or Solr database -- or you can simply let system run included ones locally.
- Can I replay Web content with my own Pywb instance? Can I replay Web content with my own OpenWayback instance?
Yes, you can configure your own Pywb instance and/or OpenWayback instance to connect directly to the LOCKSS Repository Service -- or you can let the system run included ones locally, or you can choose not to run any Web replay engine at all.
Please contact us for questions, feedback and bug reports. Open a ticket by sending e-mail to
lockss-support (at) lockss (dot) org. Your contribution toward the final LOCKSS 2.0 release is very important to us and greatly appreciated by the community.