unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Remco van 't Veer <remco@remworks.net>
Cc: help-guix@gnu.org
Subject: Re: docker containers stop when doing guix install
Date: Tue, 10 May 2022 19:47:31 +0200	[thread overview]
Message-ID: <86czgls2j0.fsf@gmail.com> (raw)
In-Reply-To: <87tu9yhi3x.fsf@remworks.net>

Hi,

On Mon, 09 May 2022 at 16:54, Remco van 't Veer <remco@remworks.net> wrote:
> 2022/05/09 15:39, zimoun:

>> Other said, how can I reproduce the bug?
>
> As follows:
>
>   $ docker ps
>   CONTAINER ID  IMAGE           COMMAND                  CREATED         STATUS        PORTS     NAMES
>   $ docker run -d postgres:10.10
>   ..
>   2b52ee072b1f5584cae597afb033cdcc0e560bbe9145b17b41502c204034e60b
>   $ docker ps
>   CONTAINER ID  IMAGE           COMMAND                  CREATED         STATUS        PORTS     NAMES
>   2b52ee072b1f  postgres:10.10  "docker-entrypoint.s…"  2 seconds ago   Up 1 seconds  5432/tcp  blah_blah
>   $ guix shell xeyes -- xeyes
>   substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
>   0.0 MB will be downloaded
>    xeyes-1.1.2  11KiB                                                                           613KiB/s 00:00 [##################] 100.0%
>   The following derivation will be built:
>     /gnu/store/xc002hxl4g8mskqmpm0grsk8s45m91gz-profile.drv
>
>   applying 4 grafts for xeyes-1.1.2 ...
>   building CA certificate bundle...
>   listing Emacs sub-directories...
>   building fonts directory...
>   building directory of Info manuals...
>   building profile with 1 package...
>   $ docker ps
>   CONTAINER ID  IMAGE           COMMAND                  CREATED         STATUS        PORTS     NAMES
>   $ exit

Thanks.

> First we see no docker containers are running, then we start postgres-10
> from docker hub, now we see its container is running, then we do
> something using guix-shell on an application *not already available on
> this system*, now the container died.  This does not work the second
> time when the "derivation" is already "built".
>
> Weird huh?

Hum, probably a bug from the ’docker-service-type’.  Could you open a
bug report by sending the information for reproducing to
bug-guix@gnu.org?


Thanks,
simon






      reply	other threads:[~2022-05-10 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  8:22 docker containers stop when doing guix install Remco van 't Veer
2022-05-09  9:01 ` zimoun
2022-05-09 10:04   ` Remco van 't Veer
2022-05-09 13:39     ` zimoun
2022-05-09 14:54       ` Remco van 't Veer
2022-05-10 17:47         ` zimoun [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86czgls2j0.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=remco@remworks.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).