Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • otbtf otbtf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Cresson Remi
  • otbtfotbtf
  • Issues
  • #25
Closed
Open
Issue created May 11, 2022 by Vincent Delbar@vincent.delbarDeveloper

Multi-stage cached docker build issues

Following discussions here, I want to suggest a new arch for the docker thing (without multistage build).
Thus allowing us to rebuild TF only when necessary.
The general idea is to use a base image of TF which is stored in subdir of the repo (like gitlab-registry.irstea.fr/remi.cresson/otbtf/base ) where every base of different TF build are stored (tags like tf-2.8.0-cpu-avx2). Then there is a second Dockerfile where the arg BASE_IMG is one of the TF base image. Finally it is pushed at the root of the repo registry.
This should ease the process of building and caching during a CI job.

Edited May 11, 2022 by Vincent Delbar
Assignee
Assign to
Time tracking