Embed custom catalog into server image


I’m running in an environment where I have no internet access and therefore I have to retag the official Rancher images and push them to my private repo. I am also running a custom catalog, which works when cloned from github.

I was thinking that since I’ve already got to retag the image, that I might as well just bake the catalog into the server image. So I created a simple Dockerfile

FROM rancher/server:v1.1.2
COPY MyCatalog /var/lib/cattle/DATA/MyCatalog

When I run this custom image it seems to start fine, and I can get to the admin UI. However, the Catalog button no longer works (and I can’t even get to the public catalog). When I look in the running server container, I see my stuff listed correctly:

root@fe36f562bd39:/var/lib/cattle/DATA# ll
total 20
drwxr-xr-x. 5 root root 4096 Jul 27 16:55 ./
drwxr-xr-x. 5 root root 4096 Jul 27 16:58 …/
drwxr-xr-x. 4 root root 4096 Jul 27 16:55 MyCatalog/
drwxr-xr-x. 10 root root 4096 Jul 27 16:56 community/
drwxr-xr-x. 6 root root 4096 Jul 27 16:56 library/

Similarly, I can see that my catalog directory structure is correct:

root@fe36f562bd39:/var/lib/cattle/DATA# find MyCatalog/ -type f

Any ideas on why the catalog feature would be unavailable after copying a custom catalog to /var/lib/cattle/DATA?

Can you check the logs during start up and show what happened during catalog-service set up?

At a minimum, the library and community catalogs should have launched cause we include them in the server.