launch

Session launch orchestration.

build_launch_spec assembles everything a provider needs to start an application container (environment, volumes, GPU, autostart script, Docker run options, which the Kubernetes backend maps onto the pod). It is used by the launch routes for new sessions and by the collaboration module when a room swaps to another application, so the two paths can no longer drift apart.

attributelogger

= logging.getLogger(__name__)

attributeDOCKER_LIST_KEYS

= ('devices', 'volumes')

attributeHARDENING_ENV

= {'harden_container': 'HARDEN_DESKTOP', 'harden_openbox': 'HARDEN_OPENBOX'}

attributeDOCKER_DICT_KEYS

= ('environment',)

attributeRUN_OPTION_PREFIXES

= ('DOCKER_', 'KUBERNETES_')

attributePOD_TEMPLATE_SETTING

= 'KUBERNETES_POD_TEMPLATE'

attributeDEFAULT_TIMEZONE

= 'Etc/UTC'

attributeRESERVED_ENV

= ('SUBFOLDER', 'PUID', 'PGID', 'CUSTOM_USER', 'PASSWORD', 'SELKIES_MASTER_TOKEN', 'SELKIES_ALLOWED_ORIGINS')

LaunchSpec