Skip to content

1.0 stable containers

No due date 100% complete

Releasing a stable set of Docker containers to the Production branch for building on the https://hub.docker.com/r/lbryio/ container registry user.

The goal will be to have a stable baseline with features including a clean, efficient, and standard method across all containers for reporting bugs. This method may improve over time but it should remain as a s…

Releasing a stable set of Docker containers to the Production branch for building on the https://hub.docker.com/r/lbryio/ container registry user.

The goal will be to have a stable baseline with features including a clean, efficient, and standard method across all containers for reporting bugs. This method may improve over time but it should remain as a single command that will be executable in the docker exec lbryio/$CONTAINERNAME debugpaste or docker-compose exec $CONTAINERNAME debugpaste it will create a temporary 90-day lifespan paste of the console output. The user can use their own discretion as to whether or not they paste the unsanitized logs. Ideally, debugpaste will warn the user if there is private data. Maybe in a future release, we will add a method for redacting sensitive data such as wallet information and IP addresses.

Containers in a release/stable state should only add or improve on features and never push a breaking change into production.

Containers in this release should be as close to the base source images as possible. Trust is paramount so we should have no secret blobs that you can't investigate yourself. Ideally, no superfluous additional features of any kind minimalism and statelessness are key.

There are no open issues in this milestone.

Add issues to milestones to help organize your work for a particular release or project.

Create new issue

Or find and add issues with no milestone in this repo.