OCI recipes do not allow setting a build path

Bug #1888257 reported by Kristian Glass
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Tom Wardill

Bug Description

I have a git repository containing multiple self-contained directories, each with an imported Dockerfile and associated data (e.g. `/traefik/{Dockerfile,entrypoint.sh}`, `/memcached/Dockerfile` etc.)

It seems like Launchpad always uses the repository root as the OCI build PATH, which requires me to modify the upstream Dockerfiles to change the source path of COPYed resources (e.g. `COPY entrypoint.sh /` in /traefik/Dockerfile needs to become `COPY traefik/entrypoint.sh /`)

I would like to instead be able to configure the build path of the OCI recipe to be a subdirectory of the repository root, and thus minimise divergence from upstream

Tags: feature lp-oci

Related branches

Changed in launchpad:
importance: Undecided → Wishlist
tags: added: feature lp-oci
Changed in launchpad:
importance: Wishlist → High
status: New → Triaged
Tom Wardill (twom)
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Tom Wardill (twom)
Tom Wardill (twom)
Changed in launchpad:
status: In Progress → Fix Committed
Tom Wardill (twom)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.