hashicorp / waypoint-examples Goto Github PK
View Code? Open in Web Editor NEWExample Apps that can be deployed with Waypoint
License: Mozilla Public License 2.0
Example Apps that can be deployed with Waypoint
License: Mozilla Public License 2.0
There is no example of how to deploy to a nomad namespace in the waypoint learning docs
https://learn.hashicorp.com/tutorials/waypoint/get-started-nomad?in=waypoint/get-started-nomad
Please considering updating the default examples to include the namespace (even if it is set to default
) to make it obvious to users how to modify the namespace.
Please provide Golang Example
I am following the documentation here: https://developer.hashicorp.com/waypoint/tutorials/deploy-aws/aws-ecs
and I cannot pass through Deploy the application with up
step.
I have running server and static runner in AWS EKS:
I can say, that server is available and connection exists. I used example repo as mentioned in docs and I can successfully Initialize the project using waypoint init
as seen here:
The problem occurs in the next step - build.
Every time I try to build an image using waypoint up
followed by docs I get:
2023-03-29T18:54:45.601+0200 [INFO] waypoint: waypoint version: full_string="v0.11.0 (e92d6fbe0)" version=v0.11.0 prerelease="" metadata="" revision=e92d6fbe0
2023-03-29T18:54:45.602+0200 [INFO] waypoint.server: attempting to source credentials and connect
2023-03-29T18:54:46.930+0200 [INFO] waypoint: server version info: version=v0.11.0 api_min=1 api_current=1 entrypoint_min=1 entrypoint_current=1
2023-03-29T18:54:46.931+0200 [INFO] waypoint: negotiated api version: version=1
2023-03-29T18:54:46.981+0200 [INFO] waypoint.runner: generated a new runner ID: id=01GWQ4P6Y5EZ0Y3ETS3PVDXZQN
2023-03-29T18:54:46.981+0200 [WARN] waypoint.runner: cookie not set for runner, will skip adoption process
2023-03-29T18:54:47.033+0200 [INFO] waypoint.runner.config_recv: new configuration received
2023-03-29T18:54:47.535+0200 [INFO] waypoint.runner: runner registered with server and ready
2023-03-29T18:54:47.537+0200 [INFO] waypoint.runner: waiting for job assignment
2023-03-29T18:54:47.590+0200 [INFO] waypoint.runner: job assignment received: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up"
2023-03-29T18:54:47.591+0200 [INFO] waypoint.runner: starting job execution: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up"
2023-03-29T18:54:47.643+0200 [INFO] waypoint.runner: register: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" plugin_name=pack type=Mapper nil=false
2023-03-29T18:54:47.643+0200 [INFO] waypoint.runner: register: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" plugin_name=pack type=Builder nil=false
2023-03-29T18:54:47.643+0200 [INFO] waypoint.runner: register: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" plugin_name=aws-ecr type=Registry nil=false
2023-03-29T18:54:47.643+0200 [INFO] waypoint.runner: register: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" plugin_name=aws-ecr type=Mapper nil=false
2023-03-29T18:54:47.643+0200 [INFO] waypoint.runner: register: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" plugin_name=aws-ecs type=Mapper nil=false
2023-03-29T18:54:47.643+0200 [INFO] waypoint.runner: register: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" plugin_name=aws-ecs type=Platform nil=false
» Performing operation locally2023-03-29T18:54:47.694+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.mapper: launching plugin: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Mapper path=/opt/homebrew/bin/waypoint args=["/opt/homebrew/bin/waypoint", "plugin", "aws-ecs"]
2023-03-29T18:54:47.744+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.mapper: initialized component: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Mapper
2023-03-29T18:54:47.746+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.mapper: launching plugin: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Mapper path=/opt/homebrew/bin/waypoint args=["/opt/homebrew/bin/waypoint", "plugin", "pack"]
2023-03-29T18:54:47.787+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.mapper: initialized component: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Mapper
2023-03-29T18:54:47.788+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.mapper: launching plugin: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Mapper path=/opt/homebrew/bin/waypoint args=["/opt/homebrew/bin/waypoint", "plugin", "aws-ecr"]
2023-03-29T18:54:47.831+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.mapper: initialized component: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Mapper
2023-03-29T18:54:47.831+0200 [INFO] waypoint.runner: project initialized: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" workspace=default
2023-03-29T18:54:47.831+0200 [INFO] waypoint.runner: executing operation: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up"
2023-03-29T18:54:47.831+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.builder: launching plugin: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Builder path=/opt/homebrew/bin/waypoint args=["/opt/homebrew/bin/waypoint", "plugin", "pack"]
» Building ecs-nodejs-web...2023-03-29T18:54:47.872+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.builder: initialized component: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Builder
2023-03-29T18:54:47.873+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.registry: launching plugin: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Registry path=/opt/homebrew/bin/waypoint args=["/opt/homebrew/bin/waypoint", "plugin", "aws-ecr"]
2023-03-29T18:54:47.915+0200 [INFO] waypoint.runner.app.ecs-nodejs-web.registry: initialized component: job_id=01GWQ4P7JR0Y852ECFFD6TRM6J job_op="*gen.Job_Up" type=Registry
⠏ Running build v16
✓ All services available.
⠏ Running build v16
✓ All services available.
✓ Set ECR Repository name to 'waypoint-example'
✓ Running build v16
✓ All services available.
✓ Set ECR Repository name to 'waypoint-example'
WARNING: Docker daemon appears unavailable. The 'pack' builder requires access to a Docker daemon. Pack does not support dockerless builds. We will still attempt to run the build but it will likely fail. If you are
running this build locally, please install Docker. If you are running this build remotely (in a Waypoint runner), the runner must be configured to have access to the Docker daemon.
✓ Running build v16
✓ All services available.
✓ Set ECR Repository name to 'waypoint-example'
WARNING: Docker daemon appears unavailable. The 'pack' builder requires access to a Docker daemon. Pack does not support dockerless builds. We will still attempt to run the build but it will likely fail. If you are
running this build locally, please install Docker. If you are running this build remotely (in a Waypoint runner), the runner must be configured to have access to the Docker daemon.
! Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the
docker daemon running?
2023-03-29T18:54:49.539+0200 [WARN] waypoint: context cancelled, stopping interrupt listener loop
How can I configure runner to have access to the Docker daemon?
I cannot find anything in documentation.
Thank you for your help.
Current
e.g.,
Proposed
"Deployment Platform"
Example
Kubernetes
Nomad
Docker
Summary
A waypoint.hcl file would be dropped into each language example for the language and platform relevant options.
It would be nice to have a Django example that also takes into account the initial seeding of the database and any eventual migration/rollback.
Describe your environment
kubernetes/nodejs-ingress
Describe the bug
waypoint up
builds and deploys the application, but gets stuck on the releasing step with the following message:
"Waiting for ingress resource to become ready...".
Steps to Reproduce
cd kubernetes/nodejs-ingress
waypoint init
waypoint up
Expected behavior
Successful release
Additional context
My environment is:
Following examples in the getting started guide : https://www.waypointproject.io/docs/getting-started
Issue :
Error in the build step of the file.
Steps performed:
The build stage failed with the first attempt
Repeating the same steps resulted in a working build.
Error log:
[detector] ======== Output: heroku/[email protected] ======== [detector] no [detector] err: heroku/[email protected] (1) [detector] ======== Output: heroku/[email protected] ======== [detector] Could not find a pom.xml file! Please check that it exists and is committed to Git. [detector] err: heroku/[email protected] (1) [detector] err: salesforce/[email protected] (1) [detector] 3 of 4 buildpacks participating [detector] heroku/nodejs-engine 0.4.4 [detector] heroku/nodejs-npm 0.2.0 [detector] heroku/procfile 0.5 2020/10/15 18:39:42.253729 INFO: ===> ANALYZING [analyzer] Previous image with name "index.docker.io/library/example-nodejs:latest" not found 2020/10/15 18:39:42.719426 INFO: ===> RESTORING 2020/10/15 18:39:43.133915 INFO: ===> BUILDING [builder] ---> Node.js Buildpack [builder] ---> Installing toolbox [builder] ---> - jq [builder] ---> - yj [builder] ---> Getting Node version [builder] ---> Resolving Node version [builder] ---> Downloading and extracting Node v12.19.0 [builder] [builder] gzip: stdin: unexpected end of file [builder] tar: Unexpected EOF in archive [builder] tar: Unexpected EOF in archive [builder] tar: Error is not recoverable: exiting now [builder] ERROR: failed to build: exit status 2
We have set up some of the example apps to use the new Waypoint splash page/home page design created by @dizzyup. This issue tracks the work to ensure that all of the apps are updated to use the same home page design and styles.
Is your feature request related to a problem? Please describe.
We have a handful of nomad examples but they don't explain the environment needed to set it up and try it out.
Describe the example scenario you wish to be included
Write a quick README to customize the nomad configuration and nomad-jobspec configuration
Would be great to see an example deploying an Elixir Phoenix app. https://www.phoenixframework.org/
Both Angular and Python are very popular with developers - both on the side of active use and on the side of "I want to learn it." Let's add example apps for both.
In our other examples, we nest examples under the top-level platform type. For example, Google Cloud Run is container orchestration that is not Kuberentes, so it has its own top-level category. This is also the same for ECS. Since AWS EKS is Kubernetes, I think it makes sense to nest it under the Kubernetes folder.
Tagging @topfunky - What do you think?
Describe your environment
Macbook Air M1 on BigSur and Docker Desktop
Describe the bug
Trying to follow the waypoint examples tutorial, tried both Nodejs and Go for Docker examples and both fail to build.
Steps to Reproduce
Run the Waypoint Examples on an M1 Mac.
Expected behavior
The error that occurs is:
2021/04/12 23:08:15.505039 DEBUG: Pulling image buildpacksio/lifecycle:0.11.1
0.11.1: Pulling from buildpacksio/lifecycle
fetching lifecycle image: no matching manifest for linux/arm64/v8 in the manifest list entries
But I expected it to continue to pass and then deploy into Docker Desktop for Mac.
Additional context
The error messages are very verbose so it's hard to tell exactly which package is breaking besides buildpacksio/lifecycle. All help is appreciated as I continue to explore the usage of Waypoint. I've got a 16" MBP to keep going on with but this will need to be fixed going forward as Apple switches everything over to M1/x chips.
Describe your environment
I'm getting issue running the waypoint-examples/aws/lambda/nodejs-graphql
example as is (with no change to the provided scripts).
Describe the bug
Running waypoint up
produces an error on the TargetGroup for Lambda:
! Creating TargetGroup for Lambda version
! ValidationError: Target group name 'waypoint-apollo-lambda-function-' cannot
begin or end with '-'
status code: 400, request id: 8a3f2f36-eb22-43af-bca8-6fdc3418b666
Steps to Reproduce
As described in the tutorials, I ran the initialization commands as follow:
waypoint install -platform=docker -accept-tos
waypoint init
which both went successful.
The waypoint.hcl
file is the same as in the example https://github.com/hashicorp/waypoint-examples/blob/main/aws/lambda/nodejs-graphql/waypoint.hcl
However, running waypoint up
produces the following outputs:
waypoint up
» Performing operation locally
» Building waypoint-apollo-lambda-function...
+ Running build v3
+ All services available.
+ Set ECR Repository name to 'waypoint-apollo-lambda'
+ Creating new repository: waypoint-apollo-lambda
+ Initializing Docker client...
+ Building image...
+ Injecting Waypoint Entrypoint...
Image built: waypoint.local/waypoint-apollo-lambda-function:latest (amd64)
+ Running push build v3
+ All services available.
+ Set ECR Repository name to 'waypoint-apollo-lambda'
+ Tagging Docker image: waypoint.local/waypoint-apollo-lambda-function:latest =>
1234567890.dkr.ecr.us-east-1.amazonaws.com/waypoint-apollo-lambda:da5c2acb0997f8390469bdce5a3dece9684a1822
+ Pushing Docker image...
│ d1f898c70255: Pushed
│ 5f70bf18a086: Pushed
│ 12048eda2ea5: Pushed
│ 3e5afe3675f2: Pushed
│ 15dd6c63f3a2: Pushed
│ c265a0dbdf5a: Pushed
│ f6999ba7b1dc: Pushed
│ 2a9a5b39a041: Pushed
│ da5c2acb0997f8390469bdce5a3dece9684a1822: digest: sha256:011901660281317186e40bb
│ e07a2c5fcf798b893bf906d46a3f8156a13ea01e8 size: 2210
+ Docker image pushed: 1234567890.dkr.ecr.us-east-1.amazonaws.com/waypoint-apollo-lambda:da5c2acb0997f8390469bdce5a3dece9684a1822
» Deploying waypoint-apollo-lambda-function...
+ Running deploy v3
+ Connecting to AWS
+ Updated Lambda configuration.
+ Updated function code!
+ Published Lambda function: arn:aws:lambda:us-east-1:1234567890:function:waypoint-apollo-lambda-function:3 (3)
! Creating TargetGroup for Lambda version
! ValidationError: Target group name 'waypoint-apollo-lambda-function-' cannot
begin or end with '-'
status code: 400, request id: 8a3f2f36-eb22-43af-bca8-6fdc3418b666
Expected behavior
It should successfully deploy the NodeJS + Graphql application.
Additional context
None.
Describe the bug
I followed step by step example in how-to guide everything is set up but deploys always failed on
Deploying... ! 2 errors occurred: * Cloud Run service failed to get ready * Error during rollback: 1 error occurred: * argument cannot be satisfied: type: bool. This is a bug in the go-argmapper library since this shouldn't happen at this point.
Steps to Reproduce
git clone https://github.com/hashicorp/waypoint-examples.git
waypoint init
waypoint up
Expected behaviour
Succesful deploy to CloudRun
Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:
Waypoint CLI Version:
CLI: v0.5.1 (76d7e17f)
Waypoint Server Platform and Version: (like docker
, nomad
, kubernetes
)
Server: v0.5.1
CloudRun, Remote k8s server
Waypoint Plugin: (like aws/ecs
, pack
, azure
)
pack
Additional context
Add any other context about the problem here.
I tried several apps and platforms node, go, python all failed with the same Error.
It happens even with Local server
My waypoint.lhci
project = "example-nodejs"
app "example-nodejs" {
labels = {
"service" = "example-nodejs",
"env" = "dev"
}
build {
use "pack" {}
registry {
use "docker" {
image = "gcr.io/hide-my-project-id/example-nodejs"
tag = "latest"
}
}
}
deploy {
use "google-cloud-run" {
project = "hide-my-project-id"
location = "europe-west3"
port = 5000
static_environment = {
"NAME" : "World"
}
capacity {
memory = 128
cpu_count = 1
max_requests_per_container = 10
request_timeout = 300
}
auto_scaling {
max = 2
}
vpc_access {
connector = "waypoint-demo"
egress = "all"
}
}
}
release {
use "google-cloud-run" {}
}
}
Is your feature request related to a problem? Please describe.
We have a handful of kubernetes examples but they don't explain the environment needed to set it up and try it out.
Describe the example scenario you wish to be included
Write a quick README in the kubernetes folder that gives some examples on how to set up a k8s environment and what might be needed to use the example. Mostly just link to existing docs and guides to help users get started.
It would be nice to have a Rails example that also takes into account the initial seeding of the database and any eventual migration/rollback.
We have the following now
Let's add
macOS Catalina 10.15.7
waypoint --version
CLI: v0.4.0 (3b3dd831)
Server: v0.4.0
waypoint-examples commit 55b8678
Issue is with example docker/ruby
waypoint.hcl
for the example is as follows:
project = "example-ruby"
app "example-ruby" {
labels = {
"service" = "example-ruby",
"env" = "dev"
}
build {
use "pack" {}
}
deploy {
use "docker" {
static_environment = {
GEM_PATH = "/layers/heroku_ruby/gems/vendor/bundle/ruby/2.6.0"
PATH = "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:bin:/layers/heroku_ruby/gems/vendor/bundle/ruby/2.6.0/bin"
}
}
}
}
Describe the bug
The waypoint up
command produces an error, and the example fails to progress beyond this point.
The error backtrace is as follows:
| [builder] -----> Installing node-v12.16.2-linux-x64
│ [builder] Command: 'set -o pipefail; curl -L --fail --retry 5 --retry-del
│ ay 1 --connect-timeout 3 --max-time 30 https://s3.amazonaws.com/heroku-nodebin/n
│ ode/release/linux-x64/node-v12.16.2-linux-x64.tar.gz -s -o - | tar zxf - node-v1
│ 2.16.2-linux-x64/bin/node' failed on attempt 1 of 3.
│ [builder] Command: 'set -o pipefail; curl -L --fail --retry 5 --retry-del
│ ay 1 --connect-timeout 3 --max-time 30 https://s3.amazonaws.com/heroku-nodebin/n
│ ode/release/linux-x64/node-v12.16.2-linux-x64.tar.gz -s -o - | tar zxf - node-v1
│ 2.16.2-linux-x64/bin/node' failed on attempt 2 of 3.
│ [builder]
│ [builder] !
│ [builder] ! Command: 'set -o pipefail; curl -L --fail --retry 5 --retry-del
│ ay 1 --connect-timeout 3 --max-time 30 https://s3.amazonaws.com/heroku-nodebin/n
│ ode/release/linux-x64/node-v12.16.2-linux-x64.tar.gz -s -o - | tar zxf - node-v1
│ 2.16.2-linux-x64/bin/node' failed unexpectedly:
│ [builder] !
│ [builder] ! gzip: stdin: invalid compressed data--format violated
│ [builder] ! tar: Unexpected EOF in archive
│ [builder] ! tar: Unexpected EOF in archive
│ [builder] ! tar: Error is not recoverable: exiting now
│ [builder] !
│ [builder] /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/shell_helpers.rb:9
│ 6:in block in run!': Command: 'set -o pipefail; curl -L --fail --retry 5 --retry
│ -delay 1 --connect-timeout 3 --max-time 30 https://s3.amazonaws.com/heroku-nodeb
│ in/node/release/linux-x64/node-v12.16.2-linux-x64.tar.gz -s -o - | tar zxf - nod
│ e-v12.16.2-linux-x64/bin/node' failed unexpectedly: (LanguagePack::Fetcher::Fetc
│ hError)
│ [builder]
│ [builder] gzip: stdin: invalid compressed data--format violated
│ [builder] tar: Unexpected EOF in archive
│ [builder] tar: Unexpected EOF in archive
│ [builder] tar: Error is not recoverable: exiting now
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/shell_h
│ elpers.rb:90:in times'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/shell_h
│ elpers.rb:90:in run!'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/fetcher
│ .rb:31:in fetch_untar'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/helpers
│ /node_installer.rb:24:in block (2 levels) in install'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/helpers
│ /node_installer.rb:23:in chdir'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/helpers
│ /node_installer.rb:23:in block in install'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/vendor/ruby/heroku-18/lib
│ /ruby/2.6.0/tmpdir.rb:93:in mktmpdir'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/helpers
│ /node_installer.rb:20:in install'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :766:in block in install_binary'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :764:in chdir'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :764:in install_binary'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :752:in block (2 levels) in install_binaries'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :752:in each'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :752:in block in install_binaries'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:18:in block (2 levels) in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:40:in yield_with_block_depth'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:17:in block in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/vendor/ruby/heroku-18/lib
│ /ruby/2.6.0/benchmark.rb:308:in realtime'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:16:in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/base.rb
│ :50:in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/base.rb
│ :46:in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :751:in install_binaries'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :170:in block in build'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :1127:in allow_git'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/ruby.rb
│ :151:in build'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/rails2.
│ rb:69:in build'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/bin/support/ruby_build:26
│ :in block (2 levels) in <main>'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/base.rb
│ :190:in log'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/bin/support/ruby_build:25
│ :in block in <main>'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:35:in block in trace'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:18:in block (2 levels) in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:40:in yield_with_block_depth'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:17:in block in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/vendor/ruby/heroku-18/lib
│ /ruby/2.6.0/benchmark.rb:308:in realtime'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:16:in instrument'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/lib/language_pack/instrum
│ ent.rb:35:in trace'
│ [builder] from /cnb/buildpacks/heroku_ruby/0.0.1/bin/support/ruby_build:21
│ :in <main>'
│ [builder] ERROR: failed to build: exit status 1
! executing lifecycle. This may be the result of using an untrusted builder:
failed with status code: 145
Steps to Reproduce
After following the exact steps documented at https://learn.hashicorp.com/tutorials/waypoint/get-started-docker?in=waypoint/get-started-docker invoke waypoint up
and wait for the build stage to fail.
Expected behavior
waypoint up
completes successfully as per the documented example in the tutorial.
Is your feature request related to a problem? Please describe.
Making the waypoint-examples repo easier to digest for people, and include more complex examples that show off new features of Waypoint.
Describe the example scenario you wish to be included
For basic examples simply showing off Waypoint at the platform, we could have those groups under a platforms
folder.
Then for more advanced features like config syncing with vault, or #52 a rails server with db migrations, we can have a features
folder to show off more complicated examples.
Describe the solution you'd like
See above.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.