You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ pkg_manager }} --setopt=tsflags=nodocs install -y {%- for package in packages %} {{ package }}{% endfor %} \
&& rpm -q{% for package in packages %} {{ package }}{% endfor %}
This was originally to reduce the amount of layers in our images, but we do not need to do that anymore since we can use more sophisticated build systems that don't result in excessive layers, and/or squashing.
But compressing things like this does make debugging issues harder because it's not always clear which part of the chain may have failed when something doesn't work. This has been a minor issue for a long time but I've just hit it fresh so I thought i'd finally raise an issue to discuss it.
The text was updated successfully, but these errors were encountered:
Generally speaking, the templating mechanism needs to be reviewed since it introduces some issues like hardcoded license or issues with extending it. It is also very complex (see #407).
Your issue seems to be a valid one, although fairly low priority. We have been using it since ages, it speeds up a little bit the build process, but I don't see any reason we couldn't drop chaining of commands.
Considering that this ticket could potentially create more layers and having the feeling that users got used to the way it is rendered I'm tempted to close this ticket without a code change. Would that be ok with you, Jon?
In the template, we do things like e.g.
This was originally to reduce the amount of layers in our images, but we do not need to do that anymore since we can use more sophisticated build systems that don't result in excessive layers, and/or squashing.
But compressing things like this does make debugging issues harder because it's not always clear which part of the chain may have failed when something doesn't work. This has been a minor issue for a long time but I've just hit it fresh so I thought i'd finally raise an issue to discuss it.
The text was updated successfully, but these errors were encountered: