Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    InitContainers never start with Azure Sql on ProGet 25.0.18

    Scheduled Pinned Locked Moved Support
    2 Posts 2 Posters 7 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C Offline
      certificatemanager_4002
      last edited by atripp

      I have a proget 25.0.18 connected to sql server. I setup dedicated pv and pvc for blobs and packages I do not have any error ate this stage. The InitContainer sequence

          initContainers:
              - name: upgradedb
                image: "proget.inedo.com/productimages/inedo/proget:25.0.18"
                command: ["/usr/local/proget/service/proget", "upgradedb"]
                env:
                  - name: PROGET_SQL_CONNECTION_STRING
                    valueFrom:
                      secretKeyRef:
                        name: connection-string
                        key: sql-connection-string
                  - name: PROGET_ENCRYPTION_KEY
                    valueFrom:
                      secretKeyRef:
                        name: encryption-key
                        key: encryption-key
      

      The pod description shows me that the initcontainer never start

      Init Containers:                                                                                                           
      │   upgradedb:                                                                                                               
      │     Container ID:                                                                                                          
      │     Image:         proget.inedo.com/productimages/inedo/proget:25.0.18                                                     │
      │     Image ID:                                                                                                              
      │     Port:          <none>                                                                                                  
      │     Host Port:     <none>                                                                                                  
      │     Command:                                                                                                               
      │       /usr/local/proget/service/proget                                                                                     
      │       upgradedb                                                                                                            
      │     State:          Waiting                                                                                                
      │       Reason:       PodInitializing                                                                                        
      │     Ready:          False                                                                                                  
      │     Restart Count:  0                                                                                                     
      │     Environment:                                                                                                           
      │       PROGET_SQL_CONNECTION_STRING:
      

      The main problem is that there is no log, so I'm not able to understand where the system failed. Is there a way to track the initcontainer.
      Regards

      atrippA 1 Reply Last reply Reply Quote -1
      • atrippA Offline
        atripp inedo-engineer @certificatemanager_4002
        last edited by

        Hi @certificatemanager_4002 ,

        I'm sorry but I'm not familiar enough with Kubernetes to help troubleshoot this issue.

        All that I recognize here is the upgradedb command, which is documented here:
        https://docs.inedo.com/docs/installation/linux/installation-upgrading-docker-containers#upgrading-the-database-only-optional

        If you run that command from the command-line (on either linux or windows), things will written to the console. I wish I could tell you why you aren't seeing the messages.

        Thanks,
        Alana

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation