Code Monkey home page Code Monkey logo

Comments (5)

pazz avatar pazz commented on September 28, 2024 1

Alright then, I will close the issue. Thanks for the pointer about build registries. I will have a look at this.
Happy new year :)

from docker-texlive.

splitt3r avatar splitt3r commented on September 28, 2024

You should do sth. like https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#sort-multi-line-arguments. And also build your own custom Docker image based on this one. Otherwise it will install the package every time your Pipeline runs.

from docker-texlive.

pazz avatar pazz commented on September 28, 2024

Sure, I could do that, but the main attraction of this project for me is that it maintains a complete texlive image that I can simply use in my CI tasks. I solved this particular case simply by checking in the outputs of bibtools..

from docker-texlive.

splitt3r avatar splitt3r commented on September 28, 2024

Yeah you are right on that point :). But adding every tool from the enormous TeX world would make this image even bigger. So the extension via an own Docker file is very straight forward way. And GitLab and GitHub have build in Registries thus it is even faster than pulling the image from Docker Hub. Which has rate limits now.

from docker-texlive.

koppor avatar koppor commented on September 28, 2024

Nice discussion. I think, this image should be a ready-to-go image for most use cases. Therefore, a JRE is included and some other tools. Making the image very large. This is sort of documented in ADR-001 and ADR-002. Need to write it down better.

Customized images should IMHO base on https://github.com/reitzig/texlive-docker. Alternatively, we should work on flavours for ourselves. Maybe, we could also write a Dockerfile generator generating the right commands based on the .tex source code to compile.

Regarding bibtool, I am a bit biased as I am the core developer of JabRef, which can also be used on the command line. I know that its startup time is slower.

The reason why the installation fails is that there is no information available on packakges any more in the image:

rm -rf /var/lib/apt/lists/* && apt-get clean

I think, bibtool is a small tool. Thus, the image size should not be significantly increased. Thus, I am trying to add it at #17.

The hint on the other registries was given at #10 (comment). Hopefully, I'll find the time to do so.

from docker-texlive.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.