posit-dev / posit-dev/images-examples

Worked example: build a Connect off-host content image from a bare OS using bakery

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cvp:2 tdp:0
Dominant language
Dockerfile
Stars
2
Forks
0
Avg merge
6d 12h
Merged PRs (30d)
2

Description

Problem

Every existing extending/ example extends a Posit-published base image (Workbench/Connect/Package Manager -min). None show the other real self-service scenario: a customer with no Posit base image, building an R/Python/Quarto execution environment from a bare OS (Ubuntu/Rocky/RHEL/etc.) for Posit Connect's off-host execution environments feature.

This is the natural companion to bakery create image --interactive (images-shared) — the wizard scaffolds and populates the Containerfile; this example is the reference a customer reads to understand what they got and why, and a hand-authored fallback for anyone not using the wizard.

Scope

  • Bare-OS base (not a Posit product image)
  • R + Python + Quarto installed via bakery's macros
  • goss tests
  • Once project-level artifact templates land (see the parent epic's dependencies), extend this example to also produce the Connect off-host values.yaml

Notes

Consider folding in Pro Drivers on a bare-OS base here rather than as a separate macro — installing Pro Drivers standalone (not depending on a Posit base image already carrying the apt/dnf repo) is a small, self-contained addition to this same example.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing examples under extending/ and the output of bakery create image --interactive in images-shared. Build a bare-OS example using bakery macros for R, Python, and Quarto, and add goss tests; completion means the example documents a working Connect off-host content image. The values.yaml extension depends on the parent epic's project-level artifact templates.

Written by the indexing model from the issue text.

Assessment

Tech stack
dockerfile, python, r
Domain
build-system, devops, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.