[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Release: Docker Image? DockerHub? skopeo?
From: |
zimoun |
Subject: |
Re: Release: Docker Image? DockerHub? skopeo? |
Date: |
Sun, 15 Nov 2020 22:30:51 +0100 |
Hi Danny,
Sorry to be late.
On Wed, 04 Nov 2020 at 15:50, Danny Milosavljevic <dannym@scratchpost.org>
wrote:
>> Some days ago, we discussed on #guix about releasing Docker images
>> ready-to-use. And you pointed your project:
>>
>> https://gitlab.com/daym/guix-on-docker/
[...]
> For the use case I'm using it for, guix-on-docker is final now.
> I doubt that I'll change anything in it, and certainly nothing major.
I have simply tried:
docker run -d --name guix registry.gitlab.com/daym/guix-on-docker
docker exec guix guix pack hello
Wow! The image is huge:
5.23GB registry.gitlab.com/daym/guix-on-docker latest 884b4a4ddf61
Is it expected? BTW, I am noting that there are couple of layers:
"RootFS": {
"Type": "layers",
"Layers": [
"sha256:c3deb477b7310360aaa445de77aa7c16f4cee76db5163c2c70573f49b2b26943",
"sha256:8128b7241acd71f13fc7bdcc5cda139e0ab75a2a987db6268d8d0f74b0974fe9",
"sha256:ba90a34fcea86f444a3ceb192ad2b6ad2d1ba86c1df4e9b4746114d86472f1a8",
"sha256:c2f9dceb24a4df38f7e708db969792ac3061270f6322411b503c347ff98399b0",
"sha256:39e027c52cb13e22b7b2a729b07e23f3574662ee482fb5c09b42c6cf51020cf6",
"sha256:5a938600c9db6ce11a1e561b2c57448a999970ebeb82539276afead86bc44319",
"sha256:541970bba9516720676f088c629ff12048ce478a2bd5e2b7da21c50feaa619f1",
"sha256:3cc6fdb7c0cc6b5bca938df9a5fa03fe3438333f3c9f686f8a90b1fc785ff07f",
"sha256:298ab852047104192cc6c5347154843f3669810c215377bcc280dbfb89277708",
"sha256:a5a94f3837bafc49d54ef88f98eb3e162e78248c8b055ab17fd057b2d57d6d2e",
"sha256:697ddc7e64d6cd06293d0840abc4876c3f27fccc70e35efd4f07d84d0e3e6d63"
]
},
I am not sure to understand why. It reminds me this previous thread:
<https://yhetil.org/guix-user/CAKjnHz1X26QhPEWZfOmAbEmZHQA1qdU_Dq7U6kVXUqG7vCvuhw@mail.gmail.com>
Well, I do not know.
Then, the ’docker exec’ downloads \o/ and then fails with:
guix pack: error: getting status of `/tmp': No such file or directory
Hum, as in the other message, I am sure I am missing the obvious with
Docker options.
> Right now, my gitlab project automatically tracks guix from git master on
> savannah and rebuilds that and pushes the result to gitlab's docker
> registry (every time someone commits to guix master).
>
> If we wanted the gitlab project to track a release tag, we'd have to
> configure it to do building from a tag, too. If so, please tell me.
Currently, it builds master, right? I have not looked but do you think
it could possible to track the both branches master and version-1.x.y?
Thanks,
simon
- Release: Docker Image? DockerHub? skopeo?, zimoun, 2020/11/04
- Re: Release: Docker Image? DockerHub? skopeo?, Jelle Licht, 2020/11/04
- Re: Release: Docker Image? DockerHub? skopeo?, Danny Milosavljevic, 2020/11/04
- Re: Release: Docker Image? DockerHub? skopeo?,
zimoun <=
- Re: Release: Docker Image? DockerHub? skopeo?, Danny Milosavljevic, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, Danny Milosavljevic, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, zimoun, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, Danny Milosavljevic, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, Danny Milosavljevic, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, Ryan Prior, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, Carlo Zancanaro, 2020/11/17
- Re: Release: Docker Image? DockerHub? skopeo?, zimoun, 2020/11/19
- Re: Release: Docker Image? DockerHub? skopeo?, Danny Milosavljevic, 2020/11/19
- /etc/passwd & co. in Docker images, Ludovic Courtès, 2020/11/20