You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Terraform uses binary plug-ins which provide various features or access cloud providers such as AWS. However there is a problem that registry does not have binaries compatible with Android (Termux).
~/test $ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding latest version of hashicorp/aws...
╷
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/hashicorp/aws v4.60.0 does not have a package available for your current platform, android_arm64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms supported.
Use of arm64 binaries for Linux may work, however all networking functionality likely would be broken because of missing /etc/resolv.conf.
~/test $ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v4.60.0...
- Installed hashicorp/aws v4.60.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
System information
termux-info:
Termux Variables:
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://packages-cf.termux.dev/apt/termux-main/ stable main
Updatable packages:
All packages up to date
termux-tools version:
1.37.0
Android version:
13
Kernel build information:
Linux localhost 4.19.261-gee74f6534678-ab9438648 #1 SMP PREEMPT Mon Dec 26 02:31:52 UTC 2022 aarch64 Android
Device manufacturer:
Google
Device model:
Pixel 5
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec.so
The text was updated successfully, but these errors were encountered:
Terraform depends on plug-in ecosystem. The plug-ins are binary
executables which are not compatible with Termux (Android). On other
hand our Terraform binary declares operating system as Android and is
unable to find plug-ins in Hashicorp registry. Both cases make the
package useless for the most of tasks.
Issue: #15869
Terraform depends on plug-in ecosystem. The plug-ins are binary
executables which are not compatible with Termux (Android). On other
hand our Terraform binary declares operating system as Android and is
unable to find plug-ins in Hashicorp registry. Both cases make the
package useless for the most of tasks.
Issue: termux/termux-packages#15869
Problem description
Terraform uses binary plug-ins which provide various features or access cloud providers such as AWS. However there is a problem that registry does not have binaries compatible with Android (Termux).
Use of
arm64
binaries for Linux may work, however all networking functionality likely would be broken because of missing/etc/resolv.conf
.I propose to disable the
terraform
package for now and look for ways of packaging the providers: https://registry.terraform.io/search/providers?namespace=hashicorp&tier=officialWhat steps will reproduce the bug?
Create
main.tf
with at least content:Run
terraform init
.What is the expected behavior?
System information
termux-info:
The text was updated successfully, but these errors were encountered: