tahoe-lafs/trac-2024-07-25

Sort out version reporting on Docker #2853

New issue

Open

opened 2016-12-19 19:54:31 +00:00 by amontero · 0 comments

amontero commented

2016-12-19 19:54:31 +00:00

Owner

Tahoe's official Docker image at https://hub.docker.com/r/tahoelafs/base/ reports version as 'unknown'. When testing beta, I thought it was a git issue or lack-of-tagging issue.
Checking old issues I found that package version is tagged at build time from previous git commits, and thus can fail.

Since the initial Docker packaging from source, Tahoe-LAFS has become easier to install with time, for example via pip.
My thoughts on this would be:

Maintain the :devel tag, build directly from source
and either:
Fix the git issue and keep building from source (I don't know enough to sort it out)
Create a different Dockerfile which installs from pip for stable releases, which does carry version info. Looks easier and cleaner. Also builds on more tested pip packaging.

I can't also assess which one is more safe, so feedback welcome.

BTW, with the added new features, node creation is better, so my WIP on 1.11 to create different Docker images for different roles (client, introducer and storage) will be far easier. Thanks!

Tahoe's official Docker image at <https://hub.docker.com/r/tahoelafs/base/> reports version as 'unknown'. When testing beta, I thought it was a git issue or lack-of-tagging issue. Checking old issues I found that package version is tagged at build time from previous git commits, and thus can fail. Since the initial Docker packaging from source, Tahoe-LAFS has become easier to install with time, for example via pip. My thoughts on this would be: - Maintain the :devel tag, build directly from source and either: - Fix the git issue and keep building from source (I don't know enough to sort it out) - Create a different Dockerfile which installs from pip for stable releases, which does carry version info. Looks easier and cleaner. Also builds on more tested pip packaging. I can't also assess which one is more safe, so feedback welcome. BTW, with the added new features, node creation is better, so my WIP on 1.11 to create different Docker images for different roles (client, introducer and storage) will be far easier. Thanks!

tahoe-lafs added the

labels 2016-12-19 19:54:31 +00:00

tahoe-lafs added this to the undecided milestone 2016-12-19 19:54:31 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2853

No description provided.