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
Building a new nextflow component always breaks the -resume functionality. This is because the container creation time is added as a LABEL to the image manifest.
The docker images is one of the sources for the hash that nextflow uses in order to trigger resume events.
Steps to reproduce
/
Expected behavior
The -resume functionality works between builds
Relevant log output
No response
Version
/
Possible solution
I would like to propose to remove this label from the docker images.
Personally I rarely used this functionality, and one could argue that the upload time metadata from the container registry is a close enough proxy for this info.
Confirmation
I have searched the existing issues to make sure this is not a duplicate.
I have provided clear and concise information about the bug.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Update: turns out that the docker label is not the root cause of this issue. After looking at some hashes with -dump-hashes, it turns out that the whole target folder is added as input for a task because we need the resources. One of items is the strict viash config, which includes metadata that is always updated each build. Note that a component might do introspection on the viash config in order to do its function.
A workaround for this issue is to add process.cache = "lenient" to the nextflow config. This is because the git_commit and git_tag properties in the build config file are always the same length, and thus the file size of the config does not change. lenient only takes into account the file name and file size.
What happened?
Building a new nextflow component always breaks the
-resume
functionality. This is because the container creation time is added as a LABEL to the image manifest.viash/src/main/scala/io/viash/platforms/DockerPlatform.scala
Line 281 in 4d7479f
The docker images is one of the sources for the hash that nextflow uses in order to trigger resume events.
Steps to reproduce
/
Expected behavior
The
-resume
functionality works between buildsRelevant log output
No response
Version
/
Possible solution
I would like to propose to remove this label from the docker images.
Personally I rarely used this functionality, and one could argue that the upload time metadata from the container registry is a close enough proxy for this info.
Confirmation
Additional context
No response
The text was updated successfully, but these errors were encountered: