aergus / dockerfiles Goto Github PK

I use your image to compile my resume and upload it, and as part of best practice I should be using a tag, instead of latest to ensure future builds don't fail. Would you consider tagging your builds so that they can then be used?

Hello,

I wonder if you could consider building a multi-architecture version of this image, to include, at least, linux/arm64 (for new M1 Macs)?

The linux/amd64 image that is available works "well" through emulation, but a native build would probably be faster.

Edit: Notes on how to do this here: https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/

Hi,

I need to install inkscape for the svg package in my Gitlab CI pipeline. However, the pipeline fails suddenly due to following apt-get errors:

$ apt-get -y update && apt-get -y install inkscape
Get:1 http://deb.debian.org/debian testing InRelease [141 kB]
Get:2 http://deb.debian.org/debian testing-updates InRelease [49.6 kB]
Get:3 http://deb.debian.org/debian-security testing-security InRelease [48.0 kB]
Reading package lists...
E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'bookworm' to 'trixie'
E: Repository 'http://deb.debian.org/debian testing-updates InRelease' changed its 'Codename' value from 'bookworm-updates' to 'trixie-updates'
E: Repository 'http://deb.debian.org/debian-security testing-security InRelease' changed its 'Codename' value from 'bookworm-security' to 'trixie-security'

It worked a few weeks ago, so it may be related to the new Debian release a few days ago?

Cheers!

Hi there,

I know you haven't pushed anything to this repo since May 10, but still there is a new build from 4 days ago on DockerHub: https://hub.docker.com/r/aergus/latex/builds/

Anyway, since this build my CI jobs fail due to missing inkscape package. It was definitely present before.

make thesis.pdf
inkscape -A images/apic-architecture.pdf images/apic-architecture.svg
make: inkscape: Command not found
make: *** [Makefile:26: images/apic-architecture.pdf] Error 127
ERROR: Job failed: exit code 1

Regards
Jack

After your recent update on 28 Jan 2019 (d91a232 and 1aa8fbe) I get the following following error when compiling a latex file that used the minted package for syntax highlighting:

Package minted Error: You must have `pygmentize' installed to use this package.

Even though python-pygments is in the Dockerfile.

Expected
Observed with the previous build before the change (which was cached on my local machine)
Image sha256 83cb44d6647e

$ which pygmentize
/usr/bin/pygmentize

Observed
With the new build
Image sha256 ec713c2b1249

$ which pygmentize
ERROR: Job failed: exit code 1

When I try to compile a LaTeX file with this image, it fails with the following error

$ apt-cache update
E: Invalid operation update
ERROR: Job failed: exit code 1

Probably that is caused by an Debian update to Bullseye.
Inside of an debian:latest image that is bullseye/sid, I can't run apt-cache update either.
However, apt-get update works.

I am using this image to run arara on tex files for my personal website. arara depends on java which is not in the image, I have to add
apt install -y default-jre as a solution to my CI.

In one of my latex builds where we use this image, we make use of convert from imagemagick (which is installed within the image), to build a high-resolution PNG version of standalone TikZ figure. Unfortunately, there is a missing security policy within the image that makes this conversion harder to achieve.

To test for this, you can start bash within the image, then do something like this:

# convert /usr/share/doc/biber/biber.pdf bla.png
convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/421.
convert-im6.q16: no images defined `bla.png' @ error/convert.c/ConvertImageCommand/3229.

To fix this, you'd have to add the security rule within the image as stated at https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion:

# #edit /etc/ImageMagick-6/policy.xml
# #comment out or delete lines like <policy domain="coder" rights="none" pattern="PDF" />
# #so it reads <!--<policy domain="coder" rights="none" pattern="PDF" />-->
# to delete, a line like this worked for me:
# sed -i '/PDF/d' /etc/ImageMagick-6/policy.xml
# #however, you may want to consider further rule removal like EPS and PS as well...

From this point, PDF -> PNG conversion should work properly from the start.

AFAICS git clone does not work for repositories fetched via SSH.
My life would be a tiny bit happier if I could have my CI build a document which is composed of several sub-documents living in git sub-modules.