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
After the update on March 1st by alexjingdbdocker, my project has started experiencing a critical issue. The Docker container built from the databricksruntime/python:13.3-LTS image no longer recognizes the project root directory, resulting in a "Module Not Found" error for my dependencies. This issue appeared immediately following the latest update and was not present in prior versions of the image.
Could the team please investigate if there were any changes in the databricksruntime/python:13.3-LTS image update that might have altered the way directories are recognized or any dependencies are handled? It seems like this update might have introduced a glitch affecting path resolution or module loading.
Thank you for looking into this matter. I am happy to provide further details or logs if needed.
PS: I would also like to address a recurring challenge with the use of mutable tags for the Docker images, such as databricksruntime/python:13.3-LTS. The mutable nature of these tags, where the underlying image can change without a corresponding change in the tag, has led to instability in my company projects on multiple occasions. This practice makes it difficult to ensure a consistent and reliable build environment, as updates can introduce unexpected behavior issues. While i appreciate your work, this has become a serious issue.
The text was updated successfully, but these errors were encountered:
Hello,
After the update on March 1st by alexjingdbdocker, my project has started experiencing a critical issue. The Docker container built from the databricksruntime/python:13.3-LTS image no longer recognizes the project root directory, resulting in a "Module Not Found" error for my dependencies. This issue appeared immediately following the latest update and was not present in prior versions of the image.
Could the team please investigate if there were any changes in the databricksruntime/python:13.3-LTS image update that might have altered the way directories are recognized or any dependencies are handled? It seems like this update might have introduced a glitch affecting path resolution or module loading.
Thank you for looking into this matter. I am happy to provide further details or logs if needed.
PS: I would also like to address a recurring challenge with the use of mutable tags for the Docker images, such as databricksruntime/python:13.3-LTS. The mutable nature of these tags, where the underlying image can change without a corresponding change in the tag, has led to instability in my company projects on multiple occasions. This practice makes it difficult to ensure a consistent and reliable build environment, as updates can introduce unexpected behavior issues. While i appreciate your work, this has become a serious issue.
The text was updated successfully, but these errors were encountered: