Project

General

Profile

Actions

Feature #1225

open

rundock updates to avoid interactive shell

Added by Hammel 1 day ago. Updated about 4 hours ago.

Status:
New
Priority:
Immediate
Assignee:
Category:
00 - Basic Build Issues
Target version:
Start date:
14 Sep 2025
Due date:
% Done:

0%

Estimated time:
Severity:
01 - Critical

Description

pibox-docker is now a separate repo that is a submodule to PiBox repos and to apps that build using the toolchain and staging trees.

There are some things to clean up in rundock so it can be used to build apps.

  • Add -a option for apps. This will cause the script to run non-interactively.
  • Add -i option to force interactive mode if -a is set.
  • Remove maps[].
  • Add RUN_ARGS supports
  • Add GID
  • Build docker image if it doesn't exist.
  • Set user= and home= on the docker command line.
  • Drop Bullseye support and make Bookworm the default.

The script should be run like this for apps:

docker/rundock -a -c "make clobber && make" ${RUN_ARGS}

This will allow the mount of the staging tree, which is handled in the Makefile, to be ephemeral.

Also: add pibox-rundock to automated backups on colo and add project to Redmine.


Related issues

Blocks PiBox - Feature #1215: Create a package for libleak and remote loggingIn ProgressHammel12 May 2025

Actions
Blocks PiBox - Feature #1224: Port all apps to use installed toolchain.In ProgressHammel13 Sep 2025

Actions
Actions #1

Updated by Hammel 1 day ago

  • Blocks Feature #1215: Create a package for libleak and remote logging added
Actions #2

Updated by Hammel 1 day ago

  • Blocks Feature #1224: Port all apps to use installed toolchain. added
Actions #3

Updated by Hammel about 20 hours ago

  • Description updated (diff)
Actions #4

Updated by Hammel about 20 hours ago

  • Description updated (diff)
Actions #5

Updated by Hammel about 4 hours ago

  • Description updated (diff)
Actions

Also available in: Atom PDF