Skip to content
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.

Creating and testing os service console images

Sven Dowideit edited this page Oct 7, 2016 · 3 revisions

I want to add some custom service containers (and develop other consoles), so I forked the rancher/os-services repo, and created a test branch.

in there, I've added some new entries to the index.yml, and then the corresponding a/alpine.yml file.

I then configured my my fresh RancherOS to read that branch's index.yml.

[root@rancher-dev rancher]# ros config set rancher.repositories.sven.url https://github.com/SvenDowideit/os-services/test/
[root@rancher-dev rancher]# ros config export
rancher:
  repositories:
    sven:
      url: https://github.com/SvenDowideit/os-services/test/
[root@rancher-dev rancher]# ros console list
disabled alpine
disabled centos
disabled centos
disabled debian
disabled debian
current  default
disabled fedora
disabled fedora
disabled ubuntu
disabled ubuntu
disabled xfce
disabled xfce

At this point (v0.7.0rc), there are duplicates because I didn't remove the existing index.yml file entries.

if the console you're developing fails to start properly, you won't be able to examine the problem, but you can reboot, and add kernel parameters to set the console back to a known working state.

unfortunately, doing so will create a new console container, losing the failed log.

If you're using the rancher/os repo, and running QEMU:

./scripts/run --append "rancher.console=default"