Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
# Motivation The `dfx` installation procedure changed. This is breaking `./scripts/docker-build`. # Changes In `Dockerfile`: 1. Add `/root/.local/share/dfx/bin` to `PATH`. 2. When installing `dfx`, set a new environment variable: `DFXVM_INIT_YES=true` Ideally, in 1, we would like to say `${HOME}/` instead of hard-coding `/root/`. I will figure out whether that is possible later, and if it is, do a second PR. For now, we want to unblock things. One thing that is blocked is seeing whether the `upload-artifact` fixes were also applied to the `Reproducible` workflow. These changes are indicated in the following places: * [forum]: Here, other users experienced similar problems. * [Slack]: Here, Eric Swanson advises us to make these changes. [forum]: https://forum.dfinity.org/t/how-do-i-install-dfx-17-0-non-interactively [Slack]: https://dfinity.slack.com/archives/CGA566TPV/p1708447484211489 # Tests Before this change, ``` ./scripts/docker-build ``` would fail. After this change, it successfully prints out WASM hashes. The fail output indicates that installing dfx exploded: ``` > [builder 17/22] RUN DFX_VERSION="$(cat config/dfx_version)" sh -c "$(curl -fsSL https://sdk.dfinity.org/install.sh)" && dfx --version: #0 0.763 Executing dfxvm install script, commit: edf3c3c87ab977366212adaadd6fdb987de396d3 #0 0.770 Downloading latest release... #0 2.861 Checking integrity of tarball... #0 2.902 dfxvm-x86_64-unknown-linux-gnu.tar.gz: OK #0 3.026 error: failed to interact with console #0 3.026 error: caused by: IO error: not a terminal #0 3.026 error: caused by: not a terminal #0 3.026 #0 3.026 Welcome to dfxvm! ``` # Todos - [x] Add entry to changelog (if necessary). # Related Bugs * http://go/jira/NNS1-2897 * http://go/jira/NNS1-2914 --------- Co-authored-by: David de Kloet <[email protected]>
- Loading branch information