Skip to content
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

Upgrade from ENV ASCIIDOCTOR_VERSION "1.5.5" to ENV ASCIIDOCTOR_VERSION "1.5.6.1" #43

Closed
patoi opened this issue Oct 2, 2017 · 5 comments

Comments

@patoi
Copy link

patoi commented Oct 2, 2017

No description provided.

@dduportal
Copy link
Contributor

Hello @patoi, thanks for your request!

Since we moved to Alpine Linux (#39) as docker base image, it raises a good question about the lifecycle of Asciidoctor version compared to the Alpine Linux lifecycle.

Currently, Alpine Linux provides:

  • Asciidoctor 1.5.5 in Alpine Linux 3.6
  • Asciidoctor 1.5.6.1 in Alpine Linux "Edge"

(source: https://pkgs.alpinelinux.org/packages?name=asciidoctor&branch=&repo=&arch=&maintainer= )

=> The maintainer of the package is Natanael Copa (@ncopa - https://github.com/ncopa ), one of the Alpine Linux creator/maintainer

=> We can expect Alpine Linux 3.7 released in ~17 days (source: https://bugs.alpinelinux.org/versions/119 ). It should embed the new asciidoctor package version.

=> Another solution would be to build (or install) our own asciidoctor without the alpine package to be able to get the "version" we want, for the price of a maintenance overhead. This is what the Docker "base" official images generally does. (Example for nginx: https://github.com/nginxinc/docker-nginx/blob/1d2e2ccae2f6e478f628f4091d8a5c36a122a157/mainline/stretch/Dockerfile )

=> We can also move away from Alpine Linux. I proposed #39 to gain some weight on the image, but this can be a solution in the future.

Hello @jirutka @mojavelinux @gscheibel : what would be your thought and advise on this pattern?

@jirutka
Copy link
Member

jirutka commented Oct 16, 2017

We can expect Alpine Linux 3.7 released in ~17 days…

Hm, I think that this release will be a bit later, we’re not in feature freeze state yet.

We can also move away from Alpine Linux.

That’s not really needed nor wise, it’d not solve this problem.

…what would be your thought and advise on this pattern?

If you want the latest version, then I’d just install asciidoctor from Rubygems instead of Aports. It doesn’t have any native extensions in the dependency graph, so it’s not a problem.

@dduportal
Copy link
Contributor

Thanks @jirutka !

I've opened #47 to implement this and upgrade the version to 1.5.6.1.

@patoi: you are welcome to help to review the PR 1.5.6.1, there is a docker image ready to pull from the docker hub to test.

@dduportal
Copy link
Contributor

Pull Request #47 have been merged: I can close this issue.

Hello @patoi: you can get the latest version of the image with the following command:

docker pull asciidoctor/docker-asciidoctor

Please feel free to re-open this issue if you are not happy with the result!

Thank you for taking care of reporting this.

@patoi
Copy link
Author

patoi commented Oct 22, 2017

Thanks to all! It works fine. @dduportal @jirutka

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants