Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-15579

DO188v4.18: Ch07: must differentiate between anon volumes as declared in Containerfiles vs anon volumes defined in compose.yaml.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • DO188 - RHOCP4.18-en-3-20250829
    • DO188
    • False
    • Hide

      None

      Show
      None
    • False
    • 7
    • en-US (English)

      Please fill in the following information:


      URL: https://role.rhu.redhat.com/rol-rhu/app/courses/do188-4.18/pages/ch07 
      Reporter RHNID: acancell@redhat.com 
      Section Title:     Compose Overview and Use Cases                                                                     

      Issue description: 

      " -V, --renew-anon-volumes: Re-create anonymous volumes."

      This is mentioned, but not clear at all how it actually works.

      Also, must differentiate between anon volumes as declared in Containerfiles (as described in previous chapters) vs anon volumes defined in compose.yaml. Example:
      ~~~
      services:
       tracker:
       volumes:
       - /appdata
      ~~~

      The latter is not described at all in the course, and the --renew-anon-volumes parameters makes sense only in this latter case. 

       

      Steps to reproduce:

       

      Workaround:

       

      Expected result:

              asernabo@redhat.com Alejandro Serna-Borja
              chetan-rhls Chetan Tiwary
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: