Homegrown docker won't start

Are you using a dockerfile to build your image and docker-compose.yml to get the container up?
Or you have an image and are using the Unraid GUI?

Verify that your containers's entry point and/or command is still correctly configured. 

is there a startup script? (such as an init script or a script specified in the CMD or ENTRYPOINT).  If yes, verify that script is in the same location and that it is executable and correctly starts.  It could also be defined in the dockerfile build.

You mentioned that there is nothing in the Docker log for this container. However, it's still a good idea to double-check by running the command docker logs <container_name_or_id> to see if there are any error messages or useful information.

Hi,

Thanks for the suggestions.

I think my problem is related to old rhel image i am using where systemd doesn't understand cgroups2.

I have read where i need to add:

 systemd.unified_cgroup_hierarchy=0 to the kernel command line OF THE HOST.

Any suggestions on how i could do that?

Kernel commands are typically controlled by the bootloader, so you owuld have to add it syslinux.cfg on the USB.
I don't usually have to mess with that and would consider it unusual.  But the steps you would take are:

 

Backup your USB drive!!

Edit syslinux.cfg, located at the root of the USB drive that Unraid boots from. The file is called syslinux.cfg, or syslinux.cfg-

Locate the append line that typically starts with append initrd=/bzroot. This is where you would add the extra kernel parameter, after the existing parameters on the append line add a space and then systemd.unified_cgroup_hierarchy=0

It would then look like this:

label Unraid OS
  menu default
  kernel /bzimage
  append initrd=/bzroot systemd.unified_cgroup_hierarchy=0

This is coloring outside of the lines for me and probably not best practice, so I can't tell you what would actually happen, or if it is supported by Limetech, as changing cgroup hierarchy can affect all containers running on the system.

Mega thanks for the help.

 

I guess i can make this change in the short term and maybe update my homegrown Rhel/systemd image (its been a few years) if it busts things.

 

Looks like Rhel 8 in 2019 got cgroups 2 support so that might be the go. 

 

Cheers Dave

the changes i made didn't fix it. I will revert to previous version and move forward to v6.12 after i have refreshed my homegrown docker.

Cheers Dave

Changed Status to Closed