<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
This PR has two goals. First of all it continues work that has been done
in #21559. Besides this, and this is more significant, I tried to
improve the structure of the documentation that is currently used for
different language-specific guides like
[PHP](https://docs.docker.com/guides/php/configure-ci-cd/),
[Go](https://docs.docker.com/guides/golang/),
[Python](https://docs.docker.com/guides/python/) and others, including,
of course, Ruby itself.
Each of these guides currently has a [Configure
CI/CD](https://docs.docker.com/guides/python/configure-ci-cd/) section.
Inside this section there is a GitHub Actions workflow example that has
nothing in common with a CI/CD pipeline. It's just an example of how to
build and push an image to a Docker Hub registry. We should be clear in
our documentation and not mislead our users. This was the main reason
why I renamed this section to "Automate your builds with GitHub
Actions". I also updated the content of this section to reflect the new
name and to make it more clear what the user can expect from this guide.
I suggest the same be done for all other language-specific guides.
Besides this, I changed the order of the sections in the Ruby guide. The
"Develop your app" section has been moved down to the bottom of the
guide. This makes more sense to me because of two reasons:
1. It is more important to start using Docker Hub right after you added
the Dockerfile to your project (section number one in all
language-specific guides).
2. I can hardly imagine anybody using Docker to run the app locally for
development purposes (at least for Ruby). What is really essential and
useful is to know how to run services, that are required by your app,
like a database, a cache server, or a local LLM. This is why the
"Develop your app" section should be rewritten to explain how to run the
infrastructure services that are required by the app and not the app
itself.
Below there are screenshots reflecting the changes that have been made
in this PR.
**Before**
<img width="1512" alt="Screenshot 2025-02-27 at 11 26 39"
src="https://github.com/user-attachments/assets/1ca06aea-ffeb-4efb-a14d-27254d2a2110"
/>
**After**
<img width="1512" alt="Screenshot 2025-02-27 at 11 26 01"
src="https://github.com/user-attachments/assets/7abbe8b7-d1b3-480f-8105-49f967b51e47"
/>
## Related issues or tickets
#21559
## Reviews
- [x] Technical review
- [x] Editorial review
- [ ] Product review
Kafbath publishes its images to Docker Hub, so changing the registry source to Hub instead of GHCR. Also, instead of using the latest tag, they publish merged changes onto a `main` tag.
The UEFI field was added
## Description
There is a difference between BIOS and UEFI, so the UEFI field is added
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
- Good callout that we should clarify that copy/pasting the certificate
values includes the `----BEGIN CERTIFICATE---` and `----END
CERTIFICATE----` lines. This applies to both Okta and Entra examples, as
confirmed in my test org
- I will pass on to IAM about adding placeholder text, I think would be
more valuable than an example in docs
## Related issues or tickets
https://github.com/docker/docs/issues/22176#event-16632900876
## Reviews
- [ ] Editorial review
<!--Delete sections as needed -->
## Description
Oversight from https://github.com/docker/docs/pull/22126. We have a
single tag being pushed.
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
<!--Delete sections as needed -->
Update release note for sign-in hang issue (PR
https://github.com/docker/pinata/pull/32513).
<!-- Tell us what you did and why -->
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
## Description
This PR updates `git clone` command for sample repositories with `&& cd
<repo name>`. Forcing to change the working directory should reduce the
risk of forgetting to do.
## Related issues or tickets
## Reviews
@usha-mandya
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
We have published and fixed CVE-2025-1696 in this release
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Move DD CLI to GA
Adds new `logs` command
Slight wording changes
`update` command now available for all OSs but have said 4.39 min
version in docs even though it's been available for mac since 4.38
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Removing the DVP statement because not all DVPs have rate limit removal.
The publisher must pay for it, and there is not visual indication of
this for users at this time of what images have rate limits removed.
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
- **chore: add testcontainers entry in the OSS section of Manuals**
- **chore: adds quickstarts for tc-go and tc-java**
<!--Delete sections as needed -->
## Description
This PR adds the Testcontainers OSS section in the Manuals > OSS section
of the docs.
It's adding the following pages:
- index page with a basic description of the project, with two cards:
- why use testcontainers, linking to a benefits page
- quicktart, linking to a folder with two pages: Go and Java
Below the cards grid, it links to the testcontainers.com/getting-started
page.
The benefits page includes some of the content of the above
getting-started page, and the Go and Java quickstart pages are copying
the quickstart pages from Go
(https://golang.testcontainers.org/quickstart/) and Java
(https://java.testcontainers.org/quickstart/) in its 3 flavours (junit4,
junit5 and spock)
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [x] Technical review
- [ ] Editorial review
- [x] Product review
---------
Co-authored-by: aevesdocker <allie.sadler@docker.com>
There might by a slight error when illustrating the
`additional_contexts` attribute. The compose file declares two services
with the same name. It might induce misunderstanding, especially since
the second service's image uses the first one to build upon.
## Description
I replaced the key defining the second service of the compose file used
to illustrate the `additional_contexts` attribute, since the key `base`
is used twice. Of course, any better replacement could be used, instead
of `my-service`.
It is invalid to use the same key twice (the error: `mapping key "base"
already defined at line 2` is expected on `docker compose up`), and it
does harm the understanding of the illustrated point of building a
service's image using another one to share layers.
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Josh Newman
Allie Sadler
Guillaume Lours
Igor Aleksandrov
Sarah Sanders
Michael Irwin
Lorena Rangel
CrazyMax
Dimitris Sotirakis
Nicolas De loof
Kaze
karman
twelsh-aw
Craig Osterhout
sheltongraves
Manuel de la Peña
Veesh Goldman
Manuel de la Peña
Etienne Guerlain
Veck Hsiao
Ville Skyttä