If you're using Dokku - especially for commercial purposes - consider donating to project development via OpenCollective or Patreon. Funds go to general development, support, and infrastructure costs.

If you'd like to sponsor specific functionality, see the project's Sponsoring document.

If you need help figuring out how to use a specific buildpack, are seeing an issue in during the buildpack process, or are having issues using multiple buildpacks, please see our slack channels or github discussion board. Issues pertaining to buildpacks may be closed and locked.

If you need support for a version of Dokku that is more than a year old, your issue may be closed without an answer. Please upgrade to a recent version.

Description of problem

When installing dokku on Oracle Linux, its stuck at - 'Runit started'

How reproducible

sudo docker container run \
   --env DOKKU_HOSTNAME=example.com \
   --env DOKKU_HOST_ROOT=/var/lib/dokku/home/dokku \
   --name dokku \
   --publish 3022:22 \
   --publish 8080:80 \
   --publish 8443:443 \
   --volume /var/lib/dokku:/mnt/dokku \
   --volume /var/run/docker.sock:/var/run/docker.sock \
   dokku/dokku:0.25.7

Steps to Reproduce

Environment used with portainer installed

[opc@portainer ~]$ cat /etc/os-release
NAME="Oracle Linux Server"
VERSION="8.4"
ID="ol"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Oracle Linux Server 8.4"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:8:4:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"

ORACLE_BUGZILLA_PRODUCT="Oracle Linux 8"
ORACLE_BUGZILLA_PRODUCT_VERSION=8.4
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=8.4

[opc@portainer ~]$ uname -a
Linux portainer 5.4.17-2102.205.7.3.el8uek.x86_64 #2 SMP Fri Sep 17 17:54:52 PDT 2021 x86_64 x86_64 x86_64 GNU/Linux

Actual Results

Expected Results

Install completion

Environment Information

dokku report APP_NAME output

This is required! Issues missing this information may be closed.

For problems affecting all applications, the report output for a broken application is useful for our debugging.
In these cases, you may run dokku report without any arguments to display the top-level reporting information.

How (deb/make/rpm) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?

Additional information

• Container Inspect Output (if applicable) via dokku ps:inspect APP_NAME
• The nginx configuration (if applicable) via dokku nginx:show-config APP_NAME
• Link to the exact repository being deployed (if possible/applicable):
• If a deploy is failing or behaving unexpectedly:
  • Application name
  • The type of application being deployed (node, php, python, ruby, etc.)
  • If using buildpacks, which custom buildpacks are in use
  • If using a Dockerfile, the contents of that file
  • If it exists, the contents of your Procfile.
• Output of failing Dokku commands after running dokku trace:on
  (BEWARE: trace:on will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXX):