unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#47617: Docker containers retain references to the runc used
@ 2021-04-06 14:42 Maxim Cournoyer
  2022-03-20 19:42 ` bug#47617: My $0.02 Christopher Rodriguez
  0 siblings, 1 reply; 2+ messages in thread
From: Maxim Cournoyer @ 2021-04-06 14:42 UTC (permalink / raw)
  To: 47617

Hello Guix!

I had this surprise today, after reconfiguring my Guix System with an
upgraded docker:

Upon attempting to run an existing container created with the previous
Docker version, I got:

--8<---------------cut here---------------start------------->8---
ERROR: for moodle-docker_db_1  Cannot start service db: Unknown runtime specified /gnu/store/jx64b4nnh6yvsbp117bfjc5spqz0jfq5-runc-1.0.0-rc6/sbin/runc
--8<---------------cut here---------------end--------------->8---

It seems the containers retain the exact references to the runc used,
and it somehow cause the execution to fail when it doesn't match with
the runc that the current Docker program is using.

The workaround is to destroy the containers and recreate them from
scratch on this upgraded Docker instance.

Thanks,

Maxim




^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#47617: My $0.02
  2021-04-06 14:42 bug#47617: Docker containers retain references to the runc used Maxim Cournoyer
@ 2022-03-20 19:42 ` Christopher Rodriguez
  0 siblings, 0 replies; 2+ messages in thread
From: Christopher Rodriguez @ 2022-03-20 19:42 UTC (permalink / raw)
  To: 47617

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

Hey,

Just ran into this issue myself. Was able to work around it by editing the
file:

`/var/run/docker/containers/<container-hash-goes-here>/hostconfig.json` to
point to the same `runc` executable that is listed by `guix package -I
runc`. After editing, simply run `sudo herd restart dockerd` and the edited
container will work as it used to.

Dunno how we might implement this kind of edit into the procedure that
updates `runc` in the first place, but it seems like that could be a
solution. Ideally, it would just use `runc` in the `$PATH`, but then `runc`
becomes a propagated input.

Hope this helps.

--

Christopher Rodriguez

[-- Attachment #2: Type: text/html, Size: 822 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-03-20 20:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-06 14:42 bug#47617: Docker containers retain references to the runc used Maxim Cournoyer
2022-03-20 19:42 ` bug#47617: My $0.02 Christopher Rodriguez

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).