#3 Disabling init container may break Peertube update

Closed
opened 4 years ago by LecygneNoir · 0 comments
Owner

Hello,

Currently, the initContainer do all the "entrypoint" process used by Peertube.

While it allows to speed up (a lot) Peertube start by avoiding the massive chown on all existing videos, it also disable the cp default that init default parameters at start.

But when Peertube is upgraded, if this cp is not done, it may miss some new parameters, which causes Peertube does not start.

So we need to find a way either to execute this cp independently of the chown, or detect new image through helm and execute the cp if a new image is used.

Hello, Currently, the initContainer do all the "entrypoint" process used by Peertube. While it allows to speed up (a lot) Peertube start by avoiding the massive chown on all existing videos, it also disable the `cp default` that init default parameters at start. But when Peertube is upgraded, if this `cp` is not done, it may miss some new parameters, which causes Peertube does not start. So we need to find a way either to execute this `cp` independently of the chown, or detect new image through helm and execute the cp if a new image is used.
LecygneNoir added the
bug
label 4 years ago
LecygneNoir closed this issue 4 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.