-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide jetty image #203
Comments
/cc @gregw from Jetty. |
FYI, I took the liberty of starting to work on a Jetty image on the model of the |
I also put up an image on the Docker Hub here: https://registry.hub.docker.com/u/mdillon/jetty The supported tags are: |
If it means we finally get the elusive @md5 to agree to be an official image maintainer, I'm definitely willing to let this one in the list of images we maintain! I've not dug in deep, but it's looking pretty reasonable so far. 👍 Are you sure you don't want to just keep it for yourself and not even involve us at the image level? 😄 url='git://github.com/md5/docker-jetty'
echo '# maintainer: Mike Dillon <mike@embody.org> (@md5)' |
I can switch it over to |
Could you guys answer my implied question about the CLA? Does Docker, Inc need to have an explicit license/copyright on official images or is that just an artifact of @infosiftr's agreement with @docker? I'll update the copyrights from "Docker, Inc" to myself if there is not a requirement to assign to Docker, Inc. |
@md5, no requirement on copyright to Docker, just expectation of reasonable updates and bug fixes. So yes it is just an artifact of our own agreement with Docker. |
I signed up for the I'll review those docs and look at creating a PR to pull |
Add AppVeyor for testing Windows builds
I'd be nice to have a jetty image based on the
_/java
one.It would have to expose tags with different combination of debian/java/jetty version, and default
:latest
to the sable combinaison (if any) of all 3.Example:
I'm not sure if a
:onbuild
version would make sense, given that:/cc @ludoch @ndeloof
The text was updated successfully, but these errors were encountered: