From: Cell <cellophan@kn1ght.org>
To: "Antonin Décimo" <antonin.decimo@gmail.com>,
"Jeroen van Veen" <jvanveen@protonmail.com>,
Cell <galene.org@kn1ght.org>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Docker image
Date: Mon, 28 Dec 2020 10:57:40 +0100 [thread overview]
Message-ID: <17F0E30F-485D-4D3A-9B43-81F7A50E3A98@kn1ght.org> (raw)
In-Reply-To: <C84B3PI4P8QJ.1T1W3VWXA7IUP@kobain>
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
Yep. That's my plan. Work in progress :)
On 28 December 2020 10:21:16 CET, "Antonin Décimo" <antonin.decimo@gmail.com> wrote:
>Hi!
>
>If your image is using a pre-compiled version of Galène, you’ll lack
>portability across distributions and architectures. You should build
>Galène and run it inside the Dockerfile. You could even use a layered
>Dockerfile so that Galène is build in one image, then copied in the
>second image and run from there.
>
>Starting from scratch is a bad idea.
>
>I’d use instead the Golang Docker image. It is well documented:
>
> https://hub.docker.com/_/golang
>
>A simple workflow would be to have the Dockerfile inside the Galène
>repo and use the example Dockerfile:
>
> FROM golang:1.15
>
> WORKDIR /go/src/galene
> COPY . .
>
> RUN go get -d -v ./...
> RUN go install -v ./...
>
> CMD ["galene"]
>
>Or you could build a "self-hosting" Dockerfile that download the
>package and its dependencies itself (this one is untested, I don't
>have the bandwidth right now):
>
> FROM golang:1.15
>
> WORKDIR /go/src/galene
> COPY data groups static ./
>
> RUN go get -d -v github.com/jech/galene
> RUN go install -v github.com/jech/galene
>
> CMD ["galene"]
>
>The Golang project provides images for Linux, Windows, macOS, and
>various architectures that you can use as base images.
>
>Once an image is build, it is *not* portable to other systems or
>architectures; but the build script (the Dockerfile) may be portable.
>For Windows, nanoserver is the lightest image, windowsservercore is a
>bit more featured.
>
>-- Antonin
[-- Attachment #2: Type: text/html, Size: 2016 bytes --]
next prev parent reply other threads:[~2020-12-28 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 17:03 [Galene] " Cell
2020-12-28 8:36 ` [Galene] " Jeroen van Veen
2020-12-28 9:21 ` Antonin Décimo
2020-12-28 9:57 ` Cell [this message]
2020-12-28 10:30 ` Juliusz Chroboczek
2020-12-28 10:42 ` Cell
2020-12-28 18:08 ` Jeroen van Veen
2021-01-26 16:58 ` Jeroen van Veen
2021-01-26 19:55 ` Juliusz Chroboczek
[not found] ` <OzDUklERX684nOGvtcdQ3NxZ5VBZumpDhMugrcaN69JCKflO-rnwI_4DJjcVPPYUUj_Hrw6kRao3SUsHzD3i9yoc1_TF_OuRyrRSNmBAc7Y=@protonmail.com>
2021-01-27 8:37 ` [Galene] Fw: " Jeroen van Veen
2021-01-26 21:01 ` [Galene] " Juliusz Chroboczek
2021-01-27 8:40 ` Jeroen van Veen
2020-12-28 9:56 ` Cell
2020-12-28 10:27 ` Juliusz Chroboczek
2020-12-28 10:11 ` Cell
2020-12-28 10:41 ` Cell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17F0E30F-485D-4D3A-9B43-81F7A50E3A98@kn1ght.org \
--to=cellophan@kn1ght.org \
--cc=antonin.decimo@gmail.com \
--cc=galene.org@kn1ght.org \
--cc=galene@lists.galene.org \
--cc=jvanveen@protonmail.com \
--subject='[Galene] Re: Docker image' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox