Cache: Cache container deleted when using in workflow with container jobs

Created on 31 Oct 2019  路  7Comments  路  Source: actions/cache

When run within a container job the action fails to run - it looks like the cache action container is deleted in the stop containers phase, before the cache post action is able to run.

Presumably, this only runs within the context of the VM, not the container context?

bug

Most helpful comment

This blocks us from migrating from CircleCI.

All 7 comments

Thanks for reporting this issue. I expect this will be a potential problem with any actions that includes a post action. We will look into it.

Update: I verified this is a bug in the runner and we are working on a fix.

What about splitting this action into two, similar to actions/upload-artifact / actions/download-artifact (also similar to what CircleCI does)?

  • actions/save-cache
  • actions/restore-cache

This will give the user a lot more control too (e.g. I might want to save the cache even before running the test steps).

@teohhanhui , would you please file another issue with your feedback, otherwise it may get lost in this issue.

Would be awesome to see this fixed guys :)

This blocks us from migrating from CircleCI.

We've rolled out an updated hosted runner that fixes for post actions in container jobs.

NICE!!! ill check it out now!

Edit:

  • updated our GH actoin, and it works! Amazing! Thanks guys!!!
Was this page helpful?
0 / 5 - 0 ratings