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
{{ message }}
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Looking at your logs, it says "Performing operation locally", which lets us know the build job is trying to happen on your local machine, and we suspect you may not have Docker running locally.
What you probably want is for the build to execute on a remote runner. If you have a default runner profile, this should happen automatically. Can you run waypoint runner profile list and see if there is a default runner profile? It should have been set automatically by the same waypoint install command that installed the server into k8s.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:How can I configure runner to have access to the Docker daemon?
I cannot find anything in documentation.
Thank you for your help.
The text was updated successfully, but these errors were encountered: