I'm trying to set the container up on Manjaro Linux (x86_64), but the build process cannot seem to execute the DaVinci Resolve AppImage file inside the container (while the same command executes properly on the host machine). The output of the last step:

STEP 10/11: RUN cd /tmp     && unzip *DaVinci_Resolve_Linux.zip     && ./*DaVinci_Resolve_*_Linux.run  --appimage-extract     && cd squashfs-root     && ./AppRun -i -a -y     && cat /tmp/squashfs-root/docs/License.txt     && rm -rf /tmp/*.run /tmp/squashfs-root /tmp/*.zip /tmp/*.pdf
Archive:  DaVinci_Resolve_Linux.zip
  inflating: DaVinci_Resolve_17.4.6_Linux.run  
  inflating: Linux_Installation_Instructions.pdf  
/bin/sh: line 1: ./DaVinci_Resolve_17.4.6_Linux.run: No such file or directory
error building at STEP "RUN cd /tmp     && unzip *DaVinci_Resolve_Linux.zip     && ./*DaVinci_Resolve_*_Linux.run  --appimage-extract     && cd squashfs-root     && ./AppRun -i -a -y     && cat /tmp/squashfs-root/docs/License.txt     && rm -rf /tmp/*.run /tmp/squashfs-root /tmp/*.zip /tmp/*.pdf": error while running runtime: exit status 127
Build of resolve:17.4.6 is complete.  To run resolve, try:

Here is what I've tried (none have worked so far):

• chmod a+x on the AppImage file in the container
• bash ./*DaVinci_Resolve_*_Linux.run --appimage-extract (as with the NVIDIA driver file - but strangely that one installs, this one doesn't run) - it then reports ./DaVinci_Resolve_17.4.6_Linux.run: cannot execute binary file.
• pre-extract the AppImage file, chmod a+x and modify Dockerfile so instead of copying the zip into the container, the AppImage is copied inside
• install fuse or fuse3 along with the dependencies (in hope that it will fix the AppImage run error)
• use Docker instead of Podman (buildah) to build the container
• sudo the build script
• revert back from kernel 5.15 to 5.10 on the host
• try the CentOS Stream 9 version on the pipewire brranch and the CentOS 8 version on the main branch (also tried with an AlmaLinux 9 base image).

I'm not sure what is missing on my end, but so far the error seems a bit cryptic to me and I can't seem to find much about how to get the container to execute the AppImage file. I'll report back here if I manage to fix the error. If anyone has suggestions, feel free to report them here. I'll also try to use another tool to extract the AppImage file's contents (as this is what the container build script is doing, too).

I've been trying a myriad of different syntaxes to add the environment variable
RESOLVE_RC_PATH=./resolve.rc
to the bash line in the desktop file and so far nothing is working.
(I need internet access to the container for use with a network library. )

Hello,
I have run some extensive tests with DaVinci Resolve Studio and did a write up about it here and in a video essay: https://trafotin.com/v/davinci-resolve

I discovered by accident that Resolve requires a static MAC address in order to stay registered. Using a random MAC address will require you to re-register Resolve every time NetworkManager restarts or reconnects. There's probably a relationship with vendor OUIs so they can limit piracy, but not exactly sure. It's the only reliable reason why they require a static MAC.

As for machine-id, if you change your machine-id to something generic, it has no impact on Resolve at all.

Hope this helps.

DaVinci Resolve (DVR) 18.5+, beta announced today, will have official Rocky Linux support:

Rocky Linux 8.6 or CentOS 7.3.

DVR-in-a-containers have worked with Rocky/Alma/Centos 9 stream already, but it's not a bad idea to make sure the build works with this older 8.x version.

Here are some issues I found with the new beta, plus quick solutions for anyone experiencing a crash on ./build.shing.

After addressing these issues, Resolve started properly on Ubuntu 23.04 (beta) with pipewire. Hopefully soon we'll have a PR to get this all in. In fact, we might want to start making:

RESOLVE_BASE_CONTAINER_IMAGE=rockylinux:8.6

The default OS if version 18.5+ is being installed just to match up with what BlackMagic Design supports officially.

Issue: DVR 18.5 has new package dependencies:

libglvnd-opengl and pulseaudio-libs are reported missing.

Solution: Add these two packages to the Dockerfile.

NOTE: Tested on Centos 8.6 and Almalinux 9 and worked for both.

Issue: Rocky Linux 8.6 doesn't know anything about:

libxcrypt-compat and compat-openssl11 (which we're using w/pipewire on centus/alma/rocky 9)

Solution for Rocky 8.6:

Pull these two packages out of the Dockerfile when building for Rocky 8.x. For Rocky 8.x, you can install compat-openssl10 for the onboarding app to work.

(Confirmed it works without them for Ubuntu 23.04 w/pipewire.)

NOTE: Removing libxcrypt-compat breaks DVR 18.5b1 on Alma Linux 9, so will have to check if they should be added or not on the fly.

Issue: DaVinci_Resolve_Welcome breaks

In almalinux 9, needs these packages: nss (for libsmime3.so), libXcomposite (for libXcomposite.so.1), libXdamage (for libXdamage.so.1) and it still needs compat-openssl10 to address the QSslSocket: issues per issue #26. This hasn't been fixed due to the security implications of an older/deprecated OpenSSL.

As mentioned, Rocky 8.6 uses compat-openssl10 to make onboarding work, even though it's deprecated.

Issue: CRB repository missing in Centos 8.6 (x264 encoder only)

If BUILD_X264_ENCODER_PLUGIN is set, the --enablerepo=crb which works nicely in centos/alma/rocky 9 is missing from Rocky 8. This repo is needed to find nasm used for making the encoder plugin.

NOTE: This breaks Alma Linux 9 build, so will have to check which to use. If anyone more familiar with the centos distro knows how to do this correctly, please respond otherwise I'll have to wing it.

Solution for Rocky 8.6:

Replacing crb with powertools in the Dockerfile seems to fix this on Rocky 8.6. At least the build crash goes away and DVR still seems to work okay.

Issue: "ed" the simple patch/text editor not found (x264 encoder only)

Solution for Rocky 8.6:

ed needs to be added to the packages to be installed in the Dockerfile if the x264 encoder is being built.

NOTE: works with Alma Linux 9 build.

If you're just trying to get the new beta to work, doing the adjustments above should be a good workaround, depending on what your host is running and the preferred image (Alama/Rocky/Centos 9 vs. Rocky 8.6). The real trick will be to make this all work in the Dockerfile but not break installations on older hosts, older container images and older versions of DVR.

Found this extensive opencl docker topic how to do opencl with amdgpu. However there are 'some' side notes considering AMD GPU support, the problem is a mix of diversity and deprecating driver support among different product lines over time. If you consider to include AMDGPU support for your container approach please continue reading. It will be a lot of IF/ELSE conditions but could be very usefull.

First we have the opensource kernel driver amdgpu which ships as the default driver in most of the linuxdistro's. This driver can be extended with MESA opensource OpenGL support, also ships in most linux distro's. Both are maintained and work great on new 5xxx 6xxx navi/big-navi to polaris RX-4xx/5xx and even the legacy GPU's GCN1-3 (HD7xxx-R9-3XX). The Mesa OpenGL performance outruns the closed source OpenGL drivers from AMD themself by huge margins and keeps improving for not only newer but also to the dated GPU's. In most distro's kernel there is also kfd besides amdgpu. This component is used to extend the free opensource kernel driver with compute capabilites closed&open source. However for some PRO graphic apps like Davinci Resolve it is required to use the closed AMDGPU Proprietary OpenGl version besides OpenCL!

This closed OpenGL driver is a first requirement since D.R. 16.1 to work with their AMD proprietary OpenCL stack (interop). Between DR 16.1 - 17, this interop proprietary OpenGL + OpenCL requirement could be worked-around, but since DR 17 it is really required! Good news is that the closed AMDGPU OpenGl driver can co-exist on the same system as with the already installed kernel AMDGPU driver and Mesa OpenGL driver and can be manually loaded/linked with SHELL Variables for specific programs.

Now the OpenCL stack on linux for AMDGPU comes offcourse again in many (forced) flavours, but it gets shipped/delivered with the same AMDGPU proprietary driver from the AMD website that also gives proprietary OpenGL.

*AMD Closed OpenCL ORCA/Legacy GCN1-4 less dated 2021 (usefull for D.R)
*AMD Closed OpenCL PAL Vega very dated 2020 (usefull for D.R)
*AMD ROCM opensource OpenCL (dated releases in the past worked for older GPUs, and newer releases might again for newer GPU's nothing in between...)
*AMD ROCR partly replaces PAL (usefull for D.R)
*Mesa Clover opensource OpenCl dated (not usefull for D.R)
*Mesa RustiCl opensource OpenCl new (not yet tested)

Around spring 2021s AMD deprecated pre-polaris GCN1-3 HD7xxx R9-3XX GPU's from the AMDGPU proprietary driver (all platforms Windows/Linux), and OpenCL support broke earlier... The good news is that newer cards (big)navi rdna1/2 still profit from a similar proprietary OpenGL rand OpenCL replacement / linking trick.

To summarize, this docker+amd Davinci Resolve support to be usefull is atleast 2 directions past/future. Detect distro/kernel version compatible with AMDGPU pro driver or add workaround for forcing the driver installing/extracting libs on other distro/kernel versions than officially supported. Than for AMDGPU's before Polaris like GCN1-3, HD7xxx R9-3XX, filter by device-id/name and download the dated older 21.20 21.30/40/50 although listed on AMD their own website broken for orca OpenCl AMDGPU proprietary driver, extract and only static link proprietary OpenGL with use of static linked Orca/legacy OpenCl for them. Not sure if they still work with newest 'amdgpu/kfd' kernel driver which comes with newer distro's still have to test. Than for newer polaris/vega/rdna1/2(big)navi download the latest and do the same identification but again with multiple directions, using OpenCl PAL or even RocM perhaps for Vega (removed since 20.40/45)?) than RoCR for anything after that like RDNA1/2?

This is offcourse a extreme simplification, but has worked in the past on seperate gpu's using different distro's. First thing to try is if I can get DR 17.x working in supported ubuntu 20.04 with 21.1030 OpenGL/OpenCL within Docker. Than try a newer D.R. 18x or maybe a newer Ubuntu and see if that works?

Nevermind the choices in AMD Vulkan landscape on linux ;-) ...

EDIT: Took the AMD proprietary driver versions suggested by Thomas Debesse.

Hi,

there is an error in the install instructions:
it is:
apt install fuse-overlayfs
not:
apt install fuseoverlayfs

Cheers,

BC

A quick note that for the just-released Resolve 18.1, the following packages are apparently now dependencies and required to be added to the Dockerfile installed packages:

apr apr-util libXinerama libxkbcommon libxkbcommon-x11 libXrandr xcb-util-image xcb-util-keysyms xcb-util-renderutil xcb-util-wm

I added these manually and it seems to be working okay. These specific packages were reported as required by the 18.1 installer:

Error: Missing or outdated system packages detected.

Please install the following missing packages:
    apr apr-util libXinerama libxkbcommon libxkbcommon-x11 
    libXrandr xcb-util-image xcb-util-keysyms 
    xcb-util-renderutil xcb-util-wm

So I added them, and the built completed without issue. I did not test to see whether they were ALL actually needed, I just blindly added them.

When running for the first time, I got a weird frozen splash screen, and had to go into the container where I saw these two processes:

QtWebEngineProc                                              
DaVinci_Resolve  

When I killed those two, suddenly DR started running, and I got this:

The libraries needed to be updated:

I decided to do a backup of the database first, just in case. You can do this by clicking on the "i" with the circle around it next to the database name.

18.0.2 told me there was a version update. I tried to update via:

sudo ./opt/resolve/DaVinci\ Control\ Panels\ Setup/DaVinci\ Control\ Panels\ Setup

It started to work..

But then didn't:

The log said:

DFU Upgrade: Getting device info.
DFU Upgrade: Waiting for initial arrival.
DFU Upgrade: Current boot mode  0
DFU Upgrade: Detaching....
DFU Upgrade: Update started.
DFU Upgrade: Payload download complete, waiting for OS arrival.
DFU Upgrade: Current boot mode  0
DFU Upgrade: Current boot mode  255
DFU Upgrade failure:  Failed to get DFU interface after download

Now when I run it and try to update I get the "Failed" dialog and this:

DFU Upgrade: Getting device info.
DFU Upgrade: Waiting for initial arrival.
DFU Upgrade: Current boot mode  255
DFU Upgrade failure:  Failed to get DFU interface before detach

The speed editor appears to still work, and I no longer get notices that there is an update. So did it update? I have no idea, but if anyone does, let me know.

(I don't have an other OS like Mac/Windows to see if there is an error w/them..)

I tried the LUTS that I was using in desktop versin of 18.6.4. The version I am using now in docker is the same version. However, it cannot find LUT. I placed it in

resolve/mounts/resolve-home/.local/share/DaVinciResolve/.LUT
also in /.local/share/DaVinciResolve/Fusion/LUTs

However, even after restart it, it doesn't show the LUTs I added.

Guys I am trying install a app, for example python, or ruby using yum install, and it works but when I close and open again it, I lose all :/

What need I modify ?
please help me, sorry i am very noob in podman

Edit 1:

I've tried follow the next tutorial from https://phoenixnap.com/kb/how-to-commit-changes-to-docker-image :

Note: after try use this guide, When I open the resolve.sh it open in bash or sh, but dont open the program and dont load the ENV, becuase if I try open resolve typing /opt/resolve/bin/resolve, i need manually add in the console __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only else davinci dont open.

PD 2: I've removed the --rm \ from resolve.sh for follow the tutorial

================================================

How to Commit Changes to a New Docker Image

The steps you must take to create a Docker image based on another image involves:

• Running a container from the base image.
• Making the necessary changes in the container.
• Committing the changes to a new image.

Follow the steps below to create a new Docker image using docker commit:

1. Use docker run with the -it flag to launch a container in the interactive mode and enable a terminal typing interface. Specify the interface shell as the last command argument.

docker run -it [image] [shell]

docker run -it ubuntu /bin/bash

apt install nmap -y

exit

docker ps -a

docker commit [container-id] [new-image-name]

docker commit c624caff45a8 ubuntu-with-nmap

docker images

================================================

Everything appears to be installed correctly. I installed the latest nvidia linux drivers on the Linux Mint 21 host before doing the installation instructions for fat-tire resolve. In Preferences in Resolve I see my Quadro T1000 card showing up with CUDA selected. But when I go to the render page I don't see h.264/5 options under Quicktime.
I had this same video card working with these options (on a previous OS build) when I installed Resolve 18 directly on Debian 11 with the makeresolvedeb script.

Any ideas why this isn't working?

So happy I found this! It worked like a charm. Previously, I was using a deb file to install Davinci Resolve. I was able to use it for weeks. However, looks like I installed some packages that ruined the libraries which affected Davinci Resolve from starting. I tried replacing libpango libglib without luck. So I tried fat-tire. OMG, it was so smooth! Thanks a lto!

Just a heads up that env-set.sh is confused if both Podman and Docker are installed (and accessible via your PATH).

The net effect is that the resolve.sh script will fail to execute Resolve (Studio).

There also should be an option to specify which container management system to utilize if more than one is installed on a host system.

I'll be creating a PR soon to fix this issue.

Hi,

I am testing this on Linux Mint 20.3. When running ./resolve.sh, I get:

docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /pulse/native

resolve.sh contains:

--mount type=bind,source=${XDG_RUNTIME_DIR}/pulse/native,target=${XDG_RUNTIME_DIR}/pulse/native \

so I guess the XDG_RUNTIME_DIR variable is not filled in . How to fix this?

Cheers
BC

When the system crash happened, I was using Davinci Resolve via fat-tire.

Now when I start it, I am now getting an error message. I don't know if it's fat-tire related or something broke in my system.
Here's the output when I start ./resolve.sh

non-network local connections being added to access control list
e611ac7fb2c1
e611ac7fb2c1
------------------------------------------------------------------------------
The container's /etc/machine-id  : f2af41ea76a20fe44741d4bb9945c1a4
The network driver setting is          : --network=none
Bind-mounted directories of interest   :
  CONTAINER (CentOS 8)                  -> HOST (Debian GNU/Linux)
  ----------------------------------------------------------------------------
  /home/resolve                         -> /home/rcamara/containers/resolve/mounts/resolve-home
  /opt/resolve/logs                     -> /home/rcamara/containers/resolve/mounts/logs
  /opt/resolve/configs                  -> /home/rcamara/containers/resolve/mounts/configs
  /opt/resolve/easyDCP                  -> /home/rcamara/containers/resolve/mounts/easyDCP
  /opt/resolve/.license                 -> /home/rcamara/containers/resolve/mounts/license
  /opt/resolve/'Resolve Disk Database'  -> /home/rcamara/containers/resolve/mounts/database
  /var/BlackmagicDesign/DaVinci Resolve -> /home/rcamara/containers/resolve/mounts/BlackmagicDesign
  /opt/resolve/Media                    -> /home/rcamara/containers/resolve/mounts/Media
docker: Error response from daemon: error gathering device information while adding custom device "/dev/nvidia-uvm": no such file or directory.

The splash screen appears and disappears almost instantly. Bisected issue to commit bba7db4 - "Force rendering on dedicated GPU", d881adb does not suffer from this.

Intel onboard graphics (not in use), GT1030 card in slot.

i am noob so please excuse

When installing some old nvidia drivers there needs to be --accept-license or is fails

like this

&& bash /tmp/NVIDIA-Linux-${ARCH}-${NVIDIA_VERSION}.run --no-kernel-module --no-kernel-module-source --run-nvidia-xconfig --no-backup --no-questions --accept-license --ui=none \

Note to self-- we may need to add something similar to this for people to add to their host to give access to the usb/hidraw devices.

File should be called something like /etc/udev/rules.d/70-blackmagic-design.rules

# BlackMagic Design hardware udev rules
# Put in /etc/udev/rules.d/70-blackmagic-design.rules

# BMD hardware (such as Speed Editor)
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1edb", TAG+="uaccess"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1edb",MODE="0660", GROUP="plugdev"

# DaVinci Resolve Studio dongle
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="096e", ATTRS{idProduct}=="0201", TAG+="uaccess"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="096e", ATTRS{idProduct}=="0201", MODE="0660", GROUP="plugdev"

Anyone want to test it? Works for me w/podman

Hi,

on Linux Mint 20.3 launching Resolve results to this in the ResolveDebug.txt:

qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Seems a QT related error in Mint. Anyone any clue on how to fix it? ldd shows no missing libraries.

Cheers,

BC

podman/docker on Ubuntu 22.04. Does look like perms issue:

bash-5.1$ touch /opt/resolve/logs/test.txt
touch: setting times of '/opt/resolve/logs/test.txt': Permission denied

Permissions seem fine:

...
drwxrwxr-x 1 resolve gary  152 Feb  4 15:06  logs
...

...so, I suspect it could be that the filesystem where my resolve folder is on the host could be the issue: ntfs-3g.

EDIT:

I moved everything to ~/resolve/, which is an ext4 filesystem, (after deleting what was in resolve/mounts/) and also tried Docker -- with success:

$ RESOLVE_RC_PATH=./resolve.rc ./resolve.sh
Running:   ./resolve.rc
./env-set.sh: line 11: ./resolve.rc: No such file or directory
non-network local connections being added to access control list
------------------------------------------------------------------------------
No "container-machine-id" file found for this container.
Creating new one derived from host machine-id (cd12b4c5318d4f3c87a8bdffc2deceda)...
This container's machine-id file can now be found at /home/gary/resolve/mounts/container-machine-id and may be replaced if needed.
The container's /etc/machine-id  : 63f5f8237a527730a494e8549b5d244d
The network driver setting is          : --network=none
Bind-mounted directories of interest   :
  CONTAINER (CentOS 8)                  -> HOST (Ubuntu)
  ----------------------------------------------------------------------------
  /home/resolve                         -> /home/gary/resolve/mounts/resolve-home
  /opt/resolve/logs                     -> /home/gary/resolve/mounts/logs
  /opt/resolve/configs                  -> /home/gary/resolve/mounts/configs
  /opt/resolve/easyDCP                  -> /home/gary/resolve/mounts/easyDCP
  /opt/resolve/.license                 -> /home/gary/resolve/mounts/license
  /opt/resolve/'Resolve Disk Database'  -> /home/gary/resolve/mounts/database
  /var/BlackmagicDesign/DaVinci Resolve -> /home/gary/resolve/mounts/BlackmagicDesign
  /opt/resolve/Media                    -> /home/gary/resolve/mounts/Media
ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
log4cxx: No appender could be found for logger (BtCommon).
log4cxx: Please initialize the log4cxx system properly.
QSocketNotifier: Can only be used with threads started with QThread
18.1.2.0006 Linux/Clang x86_64
Main thread starts: BD7A16C0
0x7ff5bd7a16c0 | Undefined            | INFO  | 2023-02-04 15:40:46,426 | --------------------------------------------------------------------------------
0x7ff5bd7a16c0 | Undefined            | INFO  | 2023-02-04 15:40:46,426 | Loaded log config from /home/resolve/.local/share/DaVinciResolve/configs/log-conf.xml
0x7ff5bd7a16c0 | Undefined            | INFO  | 2023-02-04 15:40:46,426 | --------------------------------------------------------------------------------
FusionScript Server [471] Started
Host 'Fusion' [1] Added

Podman also works. This project is impressive.

EDIT2:

I switched the filesystem used for that partition from ntfs-3g (or auto, in Ubuntu's Disk manager) to ntfs3 and Resolve launches as expected.

$ uname -r
5.15.0-60-generic

Hoping that the new ntfs3 driver proves reliable as I still need to dual-boot Win10 occasionally.

There was a problem installing

is it possible to fix this?

Manjaro
Docker version 20.10.21

./build.sh
During this build process, Blackmagic Design Pty. Ltd.'s License
Agreement for DaVinci Resolve [Studio] (18.1) will be extracted from
the zip file and displayed. You must carefully read the License Agreement
and agree to its terms and conditions before using DaVinci Resolve.
Similarly, some versions of NVIDIA's drivers also require acceptance of
a license, which is available at nvidia.com. You must review any applicable
license and agree to its terms and conditions before using the NVIDIA driver.
Do you agree to the above [y/N] y
Building the resolve:18.1 image...
WARN[0000] Reading allowed ID mappings: reading subuid mappings for user "alexandr" and subgid mappings for group "alexandr": no subuid ranges found for user "alexandr" in /etc/subuid 
WARN[0000] Found no UID ranges set aside for user "alexandr" in /etc/subuid. 
WARN[0000] Found no GID ranges set aside for user "alexandr" in /etc/subgid. 
STEP 1/16: FROM quay.io/centos/centos:stream9
Trying to pull quay.io/centos/centos:stream9...
Getting image source signatures
Copying blob 4ac1d6819b77 done  
Error: creating build container: copying system image from manifest list: writing blob: adding layer with blob "sha256:4ac1d6819b77566d3cee3dc4172247601164e2d6059757fb371b76f8f1fa411f": processing tar file(potentially insufficient UIDs or GIDs available in user namespace (requested 0:12 for /var/spool/mail): Check /etc/subuid and /etc/subgid if configured locally and run podman-system-migrate: lchown /var/spool/mail: invalid argument): exit status 1
Build of resolve:18.1 is complete.  To run resolve, try:

./resolve.sh

./resolve.sh                                                                                                                         
non-network local connections being added to access control list
./resolve.sh: строка 39: podman: команда не найдена
The 'resolve' image wasn't found.  Build the Dockerfile first.

Active development of Centos 7 (the preferred distribution by BMD for Resolve) ended in 2020. This repo currently uses Centos 8 Stream as the base container image. It would be cool to be able to lean on other RedHat derivatives like Centos 9 Stream, RockyOS and AlmaLinux.

I have manually tested most of these alternative base images however it would be good to have this as a runtime configuration parameter.

Anyone else seeing that error in podman w/Ubuntu 24.04 LTS?

If so, does removing "${CGROUP_RULE[@]}" \ from resolve.sh make a difference?

For compatibility with Arch/Majaro, make the following two mounts conditional on the source actually existing.

    --mount type=bind,source=${HOME}/.local/share/fonts,target=/usr/share/fonts,readonly (no such directory on my Manjaro machines: ~/.local/share/fonts - possibly because I installed all fonts globally?)
    --mount type=bind,source=/etc/alternatives/x-cursor-theme,target=/usr/share/icons/default/index.theme,readonly (again, the folder /etc/alternatives/x-cursor-theme does not exist)

(See here for more on cursor theme locations in Arch. The ideal situation is to inherit the same mouse theme from the host, which works currently in Ubuntu, but a more universal solution may exist (?) Perhaps a fallback value might be ~/.icons/default/index.theme with a further fallback to /usr/share/icons/default/index.theme )

Thanks @Hanziness for IDing this as an issue.

I have found that libXt.so.6 is missing for the new DaVinci Resolve 18.6.
Is it possible to add package libXt-1.1.5-12.el8.x86_64.rpm to the dnf installation step? What are the general rules for contribution?

Also, it would be nice to append in the troubleshooting part a reference to the NVIDIA article about installing and tweaking their container toolkit. I mentioned it primarily because of the issue with NVML: Insufficient Permissions and SELinux

Thank you for a good project and descriptive readme. Best regards,
NM

hi,

I have this when try to launch:

./resolve.sh
/home/pil/containers/resolve
PODMAN
/home/pil/containers/resolve
non-network local connections being added to access control list

The container's /etc/machine-id : f9e164346eb00127f7c72b8e4b951048
The network driver setting is : --network=none
Bind-mounted directories of interest :
CONTAINER (CentOS 8) -> HOST (Ubuntu)

/home/resolve -> /home/pil/containers/resolve/mounts/resolve-home
/opt/resolve/logs -> /home/pil/containers/resolve/mounts/logs
/opt/resolve/configs -> /home/pil/containers/resolve/mounts/configs
/opt/resolve/easyDCP -> /home/pil/containers/resolve/mounts/easyDCP
/opt/resolve/.license -> /home/pil/containers/resolve/mounts/license
/opt/resolve/'Resolve Disk Database' -> /home/pil/containers/resolve/mounts/database
/var/BlackmagicDesign/DaVinci Resolve -> /home/pil/containers/resolve/mounts/BlackmagicDesign
/opt/resolve/Media -> /home/pil/containers/resolve/mounts/Media
ActCCMessage Already in Table: Code= c005, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode= 0, Level= 0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode= 0, Level= 0, CmdKey= -1, Option= 0
log4cxx: No appender could be found for logger (BtCommon).
log4cxx: Please initialize the log4cxx system properly.

./resolve.sh /bin/bash give me the prompt

I have ubuntu 22.04.

any idea ?

regards,

When trying resolve image under podman I get the following error:

log4cxx: No appender could be found for logger (BtCommon).
log4cxx: Please initialize the log4cxx system properly.
Failed to create Application support Dirs

Under docker it works fine.

Trying it on Fedora 37.

Any ideas on how to solve this issue?