[INFRA-85] feat: pin provisioner image

Walkthrough

The recent updates focus on standardizing the Ubuntu version across Docker environments by introducing a UBUNTU_VERSION variable. This change affects .env example files for both mainnet and testnet, and updates the Docker Compose file to dynamically reference this new variable, ensuring consistency and ease of updates in future deployments.

Changes

File Path	Change Summary
`docker/.../.env.mainnet.example`	Added `UBUNTU_VERSION=jammy` in the "Provisioner" section.
`docker/.../.env.testnet.example`	Added `UBUNTU_VERSION=jammy` in the provisioner configuration.
`docker/addons/.../docker-compose.provisioner.yaml`	Updated service `provisioner` to use `image: ubuntu:${UBUNTU_VERSION}`.

Poem

🐰✨
In the land of code and docker files,
A rabbit hopped through digital miles.
With a tweak and hop, jammy set in place,
Now all containers run with grace.
Hop, hop, hooray, for consistency's embrace! 🎉
🐰✨

Recent Review Details

**Configuration used: CodeRabbit UI** **Review profile: CHILL**

Commits

Files that changed from the base of the PR and between 9c9c3833fe9de006c2b3e847c7b5351bb2722c1e and 69ab5014495eff5b2a14cddcd2cf4c552da2de8e.

Files selected for processing (3)

* docker/.env.mainnet.example (1 hunks) * docker/.env.testnet.example (1 hunks) * docker/addons/docker-compose.provisioner.yaml (1 hunks)

Files skipped from review due to trivial changes (2)

* docker/.env.mainnet.example * docker/.env.testnet.example

Additional comments not posted (1)

docker/addons/docker-compose.provisioner.yaml (1)
`5-5`: LGTM! This change enhances flexibility by using the `UBUNTU_VERSION` environment variable.

Verification successful
--- The verification script has successfully found the `UBUNTU_VERSION` environment variable set to `jammy` in both `docker/.env.mainnet.example` and `docker/.env.testnet.example` files. This confirms that the environment variable is correctly set in the example environment files as expected. Since the script output matches the expected result, indicating that the `UBUNTU_VERSION` is correctly configured in the relevant Docker environment files, the change in the Docker Compose file to use this environment variable is verified as correctly implemented. --- **Verification of `UBUNTU_VERSION` Environment Variable Setting** The `UBUNTU_VERSION` environment variable has been correctly set to `jammy` in both the mainnet and testnet environment files. This confirms that the Docker Compose configuration will correctly use this version for the Ubuntu image. - **File Locations:** - `docker/.env.mainnet.example` - `docker/.env.testnet.example`

Scripts Executed
The following scripts were executed for the analysis: --- Script: ```shell #!/bin/bash # Description: Verify that the `UBUNTU_VERSION` environment variable is correctly set in the environment files. # Test: Search for the `UBUNTU_VERSION` declaration in environment files. Expect: Matches. rg 'UBUNTU_VERSION=jammy' docker/.env.mainnet.example docker/.env.testnet.example ``` Length of output: 179

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

InjectiveLabs / injective-chain-releases