-
Notifications
You must be signed in to change notification settings - Fork 9
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
Issue with epub generation #9
Comments
@lmammino still reproducing? My asciidoc container info is as follows:
Try to use that specific sha so we compare the same container images. Maybe it's something else entirely too. |
I tried to run the epub script with the specific SHA you have but it seems it's not able to find that image anymore (assuming my command is correct): BOOK_SOURCE_DIR=book BOOK_BUILD_DIR=build docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor@sha256:89cf01db4a49646512b374747e1ab42ce68b3200d6c9475eba8ad40c785f77ac asciidoctor-epub3 -D $BOOK_BUILD_DIR $BOOK_SOURCE_DIR/index.adoc Output:
|
FYI, at the moment I solved this by having a local Ruby 3.3.0 install with the following Gemfile: # frozen_string_literal: true
source "https://rubygems.org"
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
ruby file: ".ruby-version"
gem 'asciidoctor'
gem 'asciidoctor-epub3'
gem 'asciidoctor-pdf'
gem 'nokogiri' And then running: bundle exec asciidoctor-epub3 --out-file build/book.epub book/index.adoc I don't know if you want to go down the path of maintaining your own docker image, but it shouldn't be to hard to create one with the necessary ruby packages... |
Ugh, oooff yes you're right I can reproduce that when I clone this repo again. and yes, I also can't find that SHA too. It looks indeed that the image setup changed and maybe they removed some of the deps which explains why you need to install them manually. I'll see about maintaining a fork or maybe there's another tag that includes them. |
and an open issue on this: asciidoctor/docker-asciidoctor#430 ;-) |
I am not sure how they are thinking to fix an issue by removing the dependency entirely, but good catch! :D And thanks for opening an issue on the official repo, probably better than going off and trying to start a fork! |
FYI: I pushed an update to pin the |
This might be a docker image versioning issue, since by default the template is configured to get the latest version of
asciidoctor/docker-aciidoctor
, but when I run:I get the following error:
Same issue if I run:
And then from within the container:
Docker image details
The text was updated successfully, but these errors were encountered: