Recently we had an issue with our DVC remote storage, which prevented us from pulling some files to a local machine. This issue has been solved, we can now run dvc pull without any errors again. However, we cannot get rid of these error messages in the Github action. When we run dvc pull there we see a bunch of these messages on Github:
WARNING: Some of the cache files do not exist neither locally nor on remote. Missing cache files
WARNING: No file hash info found for ...
However, when I connect to the very same machine where that Github action is executed and run dvc pull manually, then everything works fine. So it seems there must be some "leftover" or something (in the Docker container?) we use to run DVC/CML. How can I find the reasons for these errors on the self-hosted Github runner?
OK for the records: The problem was the dvc remote add command -
that folder was not accessible in the Docker container, I needed to mount it via the Github workflow.
Recently we had an issue with our DVC remote storage, which prevented us from pulling some files to a local machine. This issue has been solved, we can now run
dvc pull
without any errors again. However, we cannot get rid of these error messages in the Github action. When we rundvc pull
there we see a bunch of these messages on Github:However, when I connect to the very same machine where that Github action is executed and run
dvc pull
manually, then everything works fine. So it seems there must be some "leftover" or something (in the Docker container?) we use to run DVC/CML. How can I find the reasons for these errors on the self-hosted Github runner?This is how our Github workflow looks like: