Hi,
Thank you for your feedback.
On Wed, 18 Nov 2020 at 14:53, Ryan Prior wrote:
>> Multiple isolated environments on a single host
>> Preserve volume data when containers are created
>> Only recreate containers that have changed
>> Variables and moving a composition between environments
[
On November 18, 2020, Bengt Richter wrote:
> E.g., (quoted from [1]), does the following mean that the guix daemon
> potentially could run "projects"
> instead of guixbuilder* to create "Multiple isolated environments on a
> single host" ?
> The features of Compose that make it effective are:
>
>
Hi,
On +2020-11-17 17:38:09 +0100, Danny Milosavljevic wrote:
> Hi,
>
> On Sun, 15 Nov 2020 19:30:44 +0100
> zimoun wrote:
>
> > $ docker exec guix guix pack hello
> > user with UID 0 not found
>
> Docker needs to generate a /etc/passwd with uid 0 and the guix build user
> accounts, and a /et
Hi,
On Sun, 15 Nov 2020 19:30:44 +0100
zimoun wrote:
> $ docker exec guix guix pack hello
> user with UID 0 not found
Docker needs to generate a /etc/passwd with uid 0 and the guix build user
accounts, and a /etc/group with the guixbuild group; and whatever other users
the things that are com
Hi,
>> > guix pack guix -f docker -S /bin=bin \
>> >--entry-point="bin/guix-daemon --disable-chroot"
[...]
>> > Someone needs to try because the devil is in the details.
>>
>> I will try to give a try. If someone does not beat me.
>
> Please do.
I did and probably am lost in Docker det
Hi Danny,
Danny Milosavljevic skribis:
> On Fri, 06 Nov 2020 13:47:02 +0100
> zimoun wrote:
>
>> On Fri, 06 Nov 2020 at 10:59, Ludovic Courtès wrote:
>>
>> > guix pack guix -f docker -S /bin=bin \
>> >--entry-point="bin/guix-daemon --disable-chroot"
>
> Why --disable-chroot here? (I'm n
Hi,
On Fri, 06 Nov 2020 13:47:02 +0100
zimoun wrote:
> On Fri, 06 Nov 2020 at 10:59, Ludovic Courtès wrote:
>
> > guix pack guix -f docker -S /bin=bin \
> >--entry-point="bin/guix-daemon --disable-chroot"
Why --disable-chroot here? (I'm not objecting to it)
> > might work, right?
> >
>
Hi,
On Fri, 06 Nov 2020 at 10:59, Ludovic Courtès wrote:
> guix pack guix -f docker -S /bin=bin \
>--entry-point="bin/guix-daemon --disable-chroot"
>
> might work, right?
>
> Someone needs to try because the devil is in the details.
I will try to give a try. If someone does not beat me.
Hi!
Danny Milosavljevic skribis:
> On Wed, 21 Oct 2020 17:42:36 +0200
> Ludovic Courtès wrote:
>
>> zimoun skribis:
>>
>> > The tool is 'skopeo' and packaged in Guix.
>> >
>> > However, push to DockerHub requires an account (by Guix project) which
>> > requires... probably non-free JS, at lea
Hi Ludo,
On Wed, 21 Oct 2020 17:42:36 +0200
Ludovic Courtès wrote:
> zimoun skribis:
>
> > The tool is 'skopeo' and packaged in Guix.
> >
> > However, push to DockerHub requires an account (by Guix project) which
> > requires... probably non-free JS, at least once.
>
> Hmm OK. Users of Doc
Hi,
zimoun skribis:
> The tool is 'skopeo' and packaged in Guix.
>
> However, push to DockerHub requires an account (by Guix project) which
> requires... probably non-free JS, at least once.
Hmm OK. Users of Docker wouldn’t have to create an account and run the
non-free JS, so this is probably
Hi,
(adding Jelle because of 'skopeo' :-))
On Wed, 21 Oct 2020 at 11:12, Ludovic Courtès wrote:
> > Back to this. Since it would be nice to try to release (somewhere?)
> > an experimental guix Docker image.
>
> Among the issues to be addressed is whether we can push to DockerHub
> with free so
Hi,
zimoun skribis:
> Back to this. Since it would be nice to try to release (somewhere?)
> an experimental guix Docker image.
Among the issues to be addressed is whether we can push to DockerHub
with free software only (there was a discussion recently on IRC about a
tool to do that, but I don
Hi Danny,
Back to this. Since it would be nice to try to release (somewhere?)
an experimental guix Docker image.
On Thu, 24 Sep 2020 at 10:00, Danny Milosavljevic
wrote:
> Also, while doing that, using the guix binary 1.1.0 tarball from the website
> and
> issuing guix pull (ONLY), a lot of w
Also, while doing that, using the guix binary 1.1.0 tarball from the website and
issuing guix pull (ONLY), a lot of weird stuff is updated, like libx11, fribidi,
graphviz, cairo, pixman, libjpeg-turbo, pango etc. Is that really necessary?
I guess it's because of the profile hooks, but still... why
Hi,
(Sorry Dany I have overlooked this email.)
> > While I was researching gitlab, I came across a feature where they have
> > their
> > own Docker container registry on there. Apparently, the Docker CLI can
> > fetch
> > from whatever server the user wants!
> >
> > $ docker run [options] reg
Hi Danny!
On Tue, Sep 22, 2020 at 11:51:05AM +0200, Danny Milosavljevic wrote:
> Now, Heads has most of its stuff on CI servers that use Docker for a lot of
> things.
It would be very interesting to have a Docker registry for a number of
(complicated) Guix packages. We have bioinformatics package
Hello,
I'm working with Heads on using Guix to build Heads' source code reproducibly.
Now, Heads has most of its stuff on CI servers that use Docker for a lot of
things.
Therefore, I used Guix pack in the usual way to create a recent Guix
binary release and then just loaded that into a docker co
18 matches
Mail list logo
