Expected Behavior

The diagrams should be color-blind safe.

For instance, the diagrams should use shapes hashed fill styles or diagram layers to distinguish "declaring dependencies", "internal configurations", "external configurations".

For instance, what do you think if the diagram is represented as follows? (plus the arrows between items)

LAYER: dependency declaration: api, c

Just like there was an issue to make the jib.to.tags and jib.to.auth to be lazyly evaluated I would need to have the container.labels do the same. Even the reason is the same. I use com.gorylenko.gradle-git-properties Gradle plugin and would like to reuse its properties to add labels to my images. Something like that:

jib {
    container {
        labels = [
            'org.label-schema.

Describe your suggestion

When a build fails through the use of Baritone, it would be beneficial to report to the player why the build fails, whether it is an obstruction, missing material, et cetera. Having no verbose output makes troubleshooting difficult. Reporting what block is required or what external factors must be fixed would be helpful.

Settings

N/A

Context

"Unable to do