Hi, On Mon, 09 May 2022 at 16:54, Remco van 't Veer <[email protected]> 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 [email protected]? Thanks, simon
