keep installed packages when updating to newer versions #7512

Closed
opened 2025-11-02 07:28:09 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @daviddoji on GitHub (Jun 26, 2021).

  • Gitea version (or commit ref): 1.14.3
  • Git version: 2.30.2
  • Operating system: Ubuntu Server 20.04.2
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
    • MariaDB
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

Last couple of times I updated the image (from 1.14.1 to 1.14.2 and now to 1.14.3), the rendering of jupyter notebooks was lost.
However, the "app.ini" file was still modified with the instructions from the official documentation but, as the dependencies were wiped out when pulling the new image, I could not make the render. The solution was to reinstall the packages.

I do my updates by simply modifying a docker-compose file and bringing it up with docker-compose up -d.

Is there a way to keep those installed packages (for the rendering) amongst updates?

If not, is there any alternative to make the automatized the installation of the needed package?

Cheers,
David

P.S.: Thanks for making gitea :D
...

Screenshots

Originally created by @daviddoji on GitHub (Jun 26, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.14.3 - Git version: 2.30.2 - Operating system: Ubuntu Server 20.04.2 <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - [X] MariaDB - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> Last couple of times I updated the image (from 1.14.1 to 1.14.2 and now to 1.14.3), the rendering of jupyter notebooks was lost. However, the "app.ini" file was still modified with the instructions from the official documentation but, as the dependencies were wiped out when pulling the new image, I could not make the render. The solution was to reinstall the packages. I do my updates by simply modifying a docker-compose file and bringing it up with ```docker-compose up -d```. Is there a way to keep those installed packages (for the rendering) amongst updates? If not, is there any alternative to make the automatized the installation of the needed package? Cheers, David P.S.: Thanks for making gitea :D ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/questiontopic/distribution labels 2025-11-02 07:28:09 -06:00
Author
Owner

@noerw commented on GitHub (Jun 27, 2021):

Docker images are immutable, so that's expected.
The way to go is to use the official gitea docker image as a base image, where you add your custom dependencies during build time.

eg Dockerfile

FROM gitea/gitea:1.14

COPY my-binary-dep /usr/local/bin/
RUN apk install my-packaged-dep
@noerw commented on GitHub (Jun 27, 2021): Docker images are immutable, so that's expected. The way to go is to use the official gitea docker image as a base image, where you add your custom dependencies during build time. eg `Dockerfile` ``` FROM gitea/gitea:1.14 COPY my-binary-dep /usr/local/bin/ RUN apk install my-packaged-dep ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7512