-
Notifications
You must be signed in to change notification settings - Fork 80
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
Docker Compose Enhancements #136
Conversation
README.md
Outdated
When running with `docker compose` specif your revision in a file `.env` at the root of the project. The file should look like this: | ||
|
||
```bash | ||
REV=0fe2a4f28820c04ca0db07cdd44cafc98b792f3f | ||
``` |
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.
Perhaps it's better to put this env file under ./docker/compose
to make its purpose clear to somebody who stumbles upon it in the repository. Or if it must be in the root, clarify the variable's purpose like CONTAINER_REV
.
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.
Referring to a container revision in the file that is under version control in the repository that is used to produce the container is going to be cumbersome. One consequence is that you could never have a clean tree that points docker-compose to use its current revision. Maybe the checked in .env
file should be empty, or set some sensible default like latest
?
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.
Right now, we don't have a latest
flow for most delivery; we're pinning by commit hash. Doing it that way, while more cumbersome, is more deterministic. Perhaps semver to come.
We do have branch specific tags, if you look at the packages on this repo, you'll see them.
But, yes, eventually latest tags will be introduced for people just looking to play around.
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.
Perhaps it's better to put this env file under ./docker/compose to make its purpose clear to somebody who stumbles upon it in the repository. Or if it must be in the root, clarify the variable's purpose like CONTAINER_REV.
I think CONTAINER_REV makes the most sense to me. I will make the change.
…et's see if this fixes.
I believe what matters here is the underlying Docker Engine API: docker/compose#11680 So, I would essentially need to actually install Docker 26 on the runner |
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.
Looks good! One spuriously added file notwithstanding.
@@ -0,0 +1,57 @@ | |||
pub(crate) trait BackendInternalOperations { |
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.
This looks out of place; an accidental commit from the Godfig work?
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.
From Godfig
Summary
protocol-units
Small improvements to docker compose to include container testing.
Changelog
Testing