Reverting Unique DB Service Name: Avoiding Container Orphan Issues

[josep-tecnativa]

Recently, we’ve made several changes to the doodba copier template. The first one, was giving a unique name to the database service #515. As you can see in the PR, once it was merged, several problems arose. The most significant is the error PANIC: could not locate a valid checkpoint record which can appear in the database container logs on occasion.

This issue occurs because, when moving from the previous state of the template to the next one, the --remove-orphans option was not used, so the old container still exists and can cause problems.

Once we realized this, and following @PabloEForgeFlow ’s suggestion, we decided to revert those changes and differentiate the database using aliases in the default network #522.

Keep in mind that to switch from the previous state (with the unique database service name) to this new one, you also need to use the --remove-orphans option to avoid possible database problems.

If you have never used the template with the unique db service name, you don’t need to worry about this.

If you have any questions or issues, feel free to comment here.

[josep-tecnativa]

ping @Tardo