-
Notifications
You must be signed in to change notification settings - Fork 2
Deforum Dockerfile update #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Potential build break: COPY source path likely wrong for typical build context
If you build with context at the repo root (common when using -f deforum_sd/Dockerfile .), requirements.txt is usually at deforum_sd/requirements.txt. Changing to COPY ./requirements.txt . will fail unless requirements.txt was moved to the repo root. Line 44 relies on this file being present, so pip install will error if the COPY misses.
Recommended fix (assuming build context is repo root and requirements.txt remains under deforum_sd/):
If instead you build with context set to deforum_sd/ (e.g., docker build deforum_sd/), keep COPY requirements.txt . but ensure your CI/build scripts use that context consistently.
Run this script to verify where requirements.txt lives and how Docker builds are invoked:
🏁 Script executed:
Length of output: 1252
Update COPY path for requirements.txt in deforum_sd/Dockerfile
The project’s Docker build scripts invoke
docker build . -f deforum_sd/Dockerfilefrom the repo root, butrequirements.txtlives underdeforum_sd/. As a result,COPY ./requirements.txt .fails (there’s no root-level file). Update the COPY line to reference the correct path:deforum_sd/Dockerfile (around lines 43–44):
This ensures the file is found when building with context at the repository root.
📝 Committable suggestion
🤖 Prompt for AI Agents