The question refers to Tomcat as an example, but it applies to any software that is licensed under Apache 2.0 and requires configuration through configuration files.
I am creating a Docker image for Tomcat that in principle looks like the following:
FROM some-centos-base-image:1.0
ARG TOMCAT_VERSION
RUN yum install -y tomcat-${TOMCAT_VERSION}
RUN mkdir -p /code/templates
COPY entrypoint.sh /root/entrypoint.sh
COPY templates/*.xml.template /root/templates/
ENTRYPOINT [ "/root/entrypoint.sh" ]
Where templates/
is a folder with templates for Tomcat configuration files, and entrypoint.sh
is a script that simply renders the templates based on environment variables into Tomcat's configuration directory and starts Tomcat via catalina.sh run
.
The configuration file templates are derived from the example configuration files that come bundled with Tomcat, and thus have the Apache 2.0 License notice header in them.
I am about to license my project using GPLv3, and am wondering how to approach these configuration file templates. The Apache 2.0 License seems pretty clear that configuration files are covered by it, so I believe I have to respect the license in my work.
My questions:
- Am I right in that I need to respect the Apache 2.0 license in my derived project when the only part I've modified is configuration files? (if not, yay!)
- If the above is true, how do I properly include both GPLv3 and Apache 2.0 notice headers and
LICENSE
files in my project? - How do I handle the
NOTICE
file that is required by Apache 2.0? It comes with the Tomcat RPM I install and could be dependant on Tomcat version, so it seems very strange to copy-paste a version of it into my repository. - If my Docker image did not include configuration file templates, and instead required configuration by mounts (like the official Tomcat image) does, would I be free from having to handle both GPLv3 and Apache 2.0?
- Is there an example Open Source project I could refer to that is GPLv3 but includes Apache 2.0 software? As in one that has to deal with both licenses in terms of header notices,
LICENSE
files and so on.