-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add docker and docker-compose to macOS #17
Comments
This issue has not had any activity for 45 days and will be closed in 45 days if there continues to be no activity. |
Hello, thank you for your feature request. Pull request with adding docker and docker compose was merged and change would be added in next images rollout. |
2321: Add GitHub Action CI Workflow r=mergify[bot] a=bonomat Resolves #1407 This PR introduces GitHub Action CI: Within this PR we execute the following targets: * `make build` on MacOS * `make build` on Ubuntu * `make test` on Ubuntu * `make e2e` on Ubuntu Note: I've added a new make target `ci_gha` (CI GitHubActions) so that we can keep circleCI running in parallel for some time. Once we decide to completely get rid of CircleCI we can remove/rename this field. I'll create a follow-up ticket on this Not in this PR: * `make test` on MacOS as GitHub Action MacOS does not provide Docker. Aperantly this will be provided in the future though. If so, we can run tests on MacOS as well (see here: actions/runner-images#17 (comment)) * `make build/test` on Windows as we do not have an implementation for `lnd_default_dir()` for windows (see here: https://github.com/comit-network/comit-rs/blob/93f58a1762c7c7a8da038a1ec2f22dccea1a21cb/cnd/src/lib.rs#L108-L118). I will track this in another ticket once this PR is merged. Open TODOs: * create ticket to fix windows build for github actions: * create ticket to remove unneeded make target 2334: Ensure default is applied if lnd settings are not present r=D4nte a=D4nte The `Settings` struct need to always have a the lightning settings set even if not present in the file to allow the initialisation of a lnd connector in `main.rs`. Also, we use `reqwest` to target the lnd REST API so best to have a URL in the file to avoid conversion later down the stream. Co-authored-by: Philipp Hoenisch <[email protected]> Co-authored-by: Franck Royer <[email protected]>
2321: Add GitHub Action CI Workflow r=mergify[bot] a=bonomat Resolves #1407 This PR introduces GitHub Action CI: Within this PR we execute the following targets: * `make build` on MacOS * `make build` on Ubuntu * `make test` on Ubuntu * `make e2e` on Ubuntu Note: I've added a new make target `ci_gha` (CI GitHubActions) so that we can keep circleCI running in parallel for some time. Once we decide to completely get rid of CircleCI we can remove/rename this field. I'll create a follow-up ticket on this Not in this PR: * `make test` on MacOS as GitHub Action MacOS does not provide Docker. Aperantly this will be provided in the future though. If so, we can run tests on MacOS as well (see here: actions/runner-images#17 (comment)) * `make build/test` on Windows as we do not have an implementation for `lnd_default_dir()` for windows (see here: https://github.com/comit-network/comit-rs/blob/93f58a1762c7c7a8da038a1ec2f22dccea1a21cb/cnd/src/lib.rs#L108-L118). I will track this in another ticket once this PR is merged. Open TODOs: * create ticket to fix windows build for github actions: * create ticket to remove unneeded make target Co-authored-by: Philipp Hoenisch <[email protected]>
Hello, docker, docker-machine and docker-compose were added to image. If you have any concerns please feel free to reopen the issue. |
Is there anything that needs to be done for docker to be started? Our tests fail with an error from the https://github.com/comit-network/comit-rs/pull/2345/checks?check_run_id=544450918#step:8:177 |
Hello @thomaseizinger, thank you for your response. I have confirmed issue and looking into it |
This commit improves multiple aspects of Docker builds: - Enable artifact output validation for Dockerfile. - Correct the path references in Dockerfile for the distribution directory. - Add Dockerfile specific indentation rules to `.editorconfig`. - Use `npm run install-deps` for dependency installation, enhancing build reliability. - Add automation script `verify-web-server-status.js` to verify running web server on given URL. - Introduce automated build verification for Dockerfile: - On macOS, install Docker with colima as the container runtime because default agents do not include Docker and Docker runtime is not installed due to licensing issues (see actions/runner-images#17). - On Windows, there's no Linux container support (actions/runner#904, actions/runner-images#1143), so keep the checks for macOS and Ubuntu only.
Python 3.7 and earlier reached EOL earlier this year, and many tools/libraries have stopped supporting those runtimes. Continuing to support an old runtime will be near impossible due to dependency hell. It is therefore only wise to follow suit. Dependencies have been upgraded, but no other changes were required in this project; API and ABI compatibility is maintained in this version. Most of the changes were in the key dependency `eds4jinja2`, so all benefits have been derived transitively. Like `eds4jinja2`, Python versions 3.8 and 3.11 are supported and tested for. Unlike `eds4jinja2`, support for Windows and Mac OS cannot be tested due to unavailability of or problems with `docker{-compose}` on those platforms. Cross-platform commitment for this project therefore remains informal. Additionally, license has been changed from GPL to Apache. References: - actions/runner#904 - actions/runner-images#17 (comment)
Python 3.7 and earlier reached EOL earlier this year, and many tools/libraries have stopped supporting those runtimes. Continuing to support an old runtime will be near impossible due to dependency hell. It is therefore only wise to follow suit. Dependencies have been upgraded, but no other changes were required in this project; API and ABI compatibility is maintained in this version. Most of the changes were in the key dependency `eds4jinja2`, so all benefits have been derived transitively. Like `eds4jinja2`, Python versions 3.8 and 3.11 are supported and tested for. Unlike `eds4jinja2`, support for Windows and Mac OS cannot be tested due to unavailability of or problems with `docker{-compose}` on those platforms. Cross-platform commitment for this project therefore remains informal. Additionally, license has been changed from GPL to Apache. References: - actions/runner#904 - actions/runner-images#17 (comment)
This commit improves multiple aspects of Docker builds: - Enable artifact output validation for Dockerfile. - Correct the path references in Dockerfile for the distribution directory. - Add Dockerfile specific indentation rules to `.editorconfig`. - Use `npm run install-deps` for dependency installation, enhancing build reliability. - Add automation script `verify-web-server-status.js` to verify running web server on given URL. - Introduce automated build verification for Dockerfile: - On macOS, install Docker with colima as the container runtime because default agents do not include Docker and Docker runtime is not installed due to licensing issues (see actions/runner-images#17). - On Windows, there's no Linux container support (actions/runner#904, actions/runner-images#1143), so keep the checks for macOS and Ubuntu only.
As mentioned before, Docker in Mac images aren't available due to licensing issues, and probably never will. I've studied the code of https://github.com/douglascamata/setup-docker-macos-action and this seems the way to go if you need Docker AND docker compose. My only problem is that the performance inside the docker container is very bad, I couldn't extract a 25mb zip in 5 minutes. |
* Matrix the AutoGPT Python CI's `test` job across Ubuntu, macOS and Windows - Set up MinIO in a step rather than specifying it under `jobs[test].services`, because services are only supported on Linux runners - Add Windows version of step to install Poetry - Add macOS compatibility patches to 'Install Poetry (Unix)' and `setup_git_auth` steps **Caveats:** - **No Docker on macOS or Windows** * Windows comes with Docker but only supports running Windows containers, while we're mainly interested in using Linux containers for code execution and/or running auxiliary services. * [The macOS runner doesn't come with Docker](actions/runner-images#17). Setting it up is possible but takes ~3-4 minutes, and the performance of the Colima engine is poor: a `docker pull` that takes 2 seconds on Linux takes 45 seconds on macOS. - **No S3 service available on Windows** It seems that running a background process [isn't possible on Windows](actions/runner#598 (comment)), and neither is running Linux-based Docker containers. * Add `autogpt-agent` and OS-specific flags to Codecov upload step * Improve caching of Python dependencies in CI by changing the cache key - Include hash of `poetry.lock` instead of `pyproject.toml` in key - Remove date component from key; it was included to avoid getting stuck to old cached versions of packages when we were still using `requirements.txt`. With `poetry.lock` that is no longer a concern. * Fix skip check in test_s3_file_storage.py
Switch to a different action to install docker on Mac OS, the current one seems to be problematic. https://github.com/marketplace/actions/setup-docker-on-macos Useful references about the issue: actions/runner-images#17 docker-practice/actions-setup-docker#29 Signed-off-by: Diego Rondini <[email protected]>
Switch to a different action to install docker on Mac OS, the current one seems to be problematic. https://github.com/marketplace/actions/setup-docker-on-macos Useful references about the issue: actions/runner-images#17 docker-practice/actions-setup-docker#29 Signed-off-by: Diego Rondini <[email protected]>
Tool information
Virtual environments affected
Already exists on the Windows and Linux environments.
Can this tool be installed during the build?
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: