You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, awesome project, thank you so much! I'm currently trying to use this in a secondary workflow. I know it works - because we already rely on it to build redis for redis-stack. But, I'm extremely confused because what should be simple reuse (i.e call it again) clearly builds the docker, but then it fails to run a simple command such as ls, as evident by this action run, even though the use is near identical.
However, I did notice that the runner output now contains the following
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Any chance you can help shed light on this? I'm stumped!
The text was updated successfully, but these errors were encountered:
Hi!
First of all, awesome project, thank you so much! I'm currently trying to use this in a secondary workflow. I know it works - because we already rely on it to build redis for redis-stack. But, I'm extremely confused because what should be simple reuse (i.e call it again) clearly builds the docker, but then it fails to run a simple command such as
ls
, as evident by this action run, even though the use is near identical.However, I did notice that the runner output now contains the following
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Any chance you can help shed light on this? I'm stumped!
The text was updated successfully, but these errors were encountered: