View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007511 | Taler | deployment and operations | public | 2022-12-07 16:45 | 2022-12-08 13:39 |
| Reporter | MS | Assigned To | MS | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0007511: Consider keep intermediate containers along the Docker base image builder. | ||||
| Description | After Gv's rapid disk memory consumption, the base script builder ([0]) was patched by using "--force-rm" when building the base image, unconditionally. That made difficult to obtain a shell when the _sources compilation_ failed, however. Even when the base image will be entirely based on DEB packages, errors may still happen along the build phase and therefore a shell to the last container can be helpful. So possibly "--force-rm" should be made optional. 0: deployment/docker/demo/build_base.sh | ||||
| Tags | No tags attached. | ||||