Not possible to access init container logs

[iamdanthedev]

Please provide us with the following information:

This issue is a: (mark with an x)

• bug report -> please search issues before submitting
• documentation issue or request
• regression (a behavior that used to work and stopped in a new release)

Issue description

A clear and concise description of the observed issue.

Steps to reproduce

1. Configure initContainers similar to

      initContainers: [
        {
          name: 'migration-up-runner'
          image: '${crName}.azurecr.io/migration_up:${dockerTag}'
          env: dbEnvVars
          resources: {
            cpu: '0.25'
            memory: '0.5Gi'
          }
        }
      ]

2. The container probably throws an error during execution
3. Go to System logs / Console logs
4. No execution logs appear

To be fair, I did see the logs 1 time out of 20 deployments, and I am not sure what made it work. I tried all different combinations of ENTRYPOINT, command, command + args

Expected behavior [What you expected to happen.]
I expect to go to Console Logs and see init container execution logs in order to debug the problem

Actual behavior [What actually happened.]
The logs are nowhere to be found

Screenshots
If applicable, add screenshots to help explain your problem.

[alicyn]

I am having the same issue, cannot see logs from init containers at all.

I tried:
az containerapp logs show -n <containerapp_name> -g <resource_group> --follow --revision <revision_name> --container <init_container_name> --type console

result:
Could not find container

[vinisoto]

Hi, we are working on a fix for this issue. Will update here when the fix is completed.

[ractando]

@vinisoto is the fix applied for this issue?

[kobeyy]

We are experiencing exactly the same issue. Our database migration script fails but we are not able to view the logs which makes debugging really hard.

@vinisoto any update?

We are in the progress of migrating ~30 backend services from AKS to container apps. Would really appreciate an update regarding this issue. Depending on the timeframe we might need to delay the roll out.

[iamdanthedev]

By the way for us this problem got resolved somehow by itself somewhere around early autumn. I can see log messages coming from the init container in the regular Console Logs section.

[vinisoto]

@kobeyy - this issue should be resolved. If you are still experiencing issues, please send us an email at acasupport at microsoft dot com with you subscription id, container app name and timeframe of missing logs

[JPeer264]

Not sure if this is related since mine is within ACIs.

The Azure dashboard itself always shows "Loading..." when the init containers are still running (State = Running). Over the CLI, however, I get an error stating the container group is not yet ready:

$ az container logs --name <container_group> --container-name <container_name> --resource-group <resource_group>
# (ContainerGroupDeploymentNotReady) The container group '<container_group>' is not ready for the operation.
# Code: ContainerGroupDeploymentNotReady
# Message: The container group '<container_group>' is not ready for the operation.

In the Azure dashboard the logs are shown when State = Terminated.
However, as soon as the init container has finished (State = Terminated) then the logs can be seen both in the dashboard and the CLI (assuming the same command is executed as before).

[bandwiches]

Issue persists as of Dec 2024. It's confusing at best whether this is resolved or being worked on.

Confirmed Workaround: export to log analytics

---

This issue was opened May 2023. Latest update was Dec 2023:

@kobeyy - this issue should be resolved. If you are still experiencing issues, please send us an email at acasupport at microsoft dot com with you subscription id, container app name and timeframe of missing logs

This issue remains open to this day (Dec 2024) despite being "resolved".

---

#1336 was opened Nov 2024 and appears to be the same issue. Last update on Nov 7 was:

Thank you guys for raising this, we've added this to the backlog of our public roadmap. If you find yourself in the same situation and need this issue fixed please upvote here for us to get prioritization signal.