Public Repository

Last pushed: a year ago
Short Description
Short description is empty for this repo.
Full Description

Full description is empty for this repo.

Docker Pull Command

Comments (3)
8 months ago

@atwong: I have a comment on the appropriate docker issue #7459 detailing my testing & findings on how to get SystemD working inside a docker container.

So to start this, you need to do something like this:

docker run -t -i --privileged -v /sys/fs/cgroup:/sys/fs/cgroup -v /var/run/dbus:/var/run/dbus -e 'container=docker' trinitronx/minera

Note that you may also opt to avoid the -ti options for interactive mode, and just pass in -d instead to run it in daemon mode.

8 months ago

@atwong: Hello! Thanks for trying out the minera docker container! So it looks like I forgot to document a basic thing having to do with this container: because it uses SystemD inside the container, you need to run it with a couple options:

  • -v /sys/fs/cgroup:/sys/fs/cgroup to pass in the host kernel's cgroup hierarchy (SystemD is throwing an error about this in your log)
  • -v /var/run/dbus:/var/run/dbus in order to start services that require DBus (Ubuntu has some of these), you need to pass in the host's DBus daemon socket
  • -e 'container=docker' A bit peculiar, but apparently in some versions of SystemD, this environment variable tells it that it is running inside a container so it can handle starting in this special case.
8 months ago

Doesn't work....

ovpn-117-51:sandbox alwong$ docker run -t -i --privileged trinitronx/minera
mount: /sys/fs/cgroup is busy
Failed to insert module 'autofs4': No such file or directory
Detected virtualization docker.
Detected architecture x86-64.

Welcome to Debian GNU/Linux stretch/sid!

Set hostname to <b2308a939c50>.
Cannot determine cgroup we are running in: No medium found
Failed to allocate manager object: No medium found
[!!!!!!] Failed to allocate manager object, freezing.
Freezing execution.