Building upon base layer

[grantmacken]

I want to argue the case, for keeping the base layer as simple as practicable and then layering use cases into tagged images.

Obviously, when it comes to docker images, size matters. Once you have a layer in place, it is easy to add/subtract stuff and give it a tag. You could say have a v3.4.1-teiPub tag with the eXist TEI Publisher env preinstalled.

The trick is deciding what should be in and what should be out of the base layer.
Please add suggestions, comments.

• Out: /bin - reason: no shell
• Out: /tests - reason: its all ready been tested

[adamretter]

I agree that we can drop /bin and /tests

[duncdrum]

I actually think that /tests should be excluded by the minimal build flag if it isn't already. No objections to removing bin/

[duncdrum]

I also like the idea of use-case images, maybe we can discuss ideas in a video call.

[adamretter]

I like the idea of use-case images, but not produced by us. We have limited resources. If the TEI-Publisher people want a TEI-Publisher docker image, we should give them the tools to create such a thing, but not do it for them.