Skip to content
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

Getting started guide did not get me started #1558

Closed
githubcdr opened this issue Nov 23, 2022 · 5 comments
Closed

Getting started guide did not get me started #1558

githubcdr opened this issue Nov 23, 2022 · 5 comments
Labels
status/triage Issue or PR that requires contributor attention. type/bug Issue that reports an unexpected behaviour.

Comments

@githubcdr
Copy link

Summary

As a news user I can't get the sample to work

Reproduction

Follow the getting started guide

Steps

pack build my-app --buildpack paketo-buildpacks/nodejs \  ✔
--builder heroku/buildpacks:20

ERROR: failed to build: invalid builder heroku/buildpacks:20: builder index.docker.io/heroku/buildpacks:20 missing label io.buildpacks.builder.metadata -- try recreating builder

Current behavior

I would expect to have valuable info what is going wrong, is this my fault, is this a bug?

Expected behavior

Environment

pack info
docker info
@githubcdr githubcdr added status/triage Issue or PR that requires contributor attention. type/bug Issue that reports an unexpected behaviour. labels Nov 23, 2022
@natalieparellano
Copy link
Member

@githubcdr I think this may be due to mixing Paketo buildpacks with the Heroku builder. Can you try pack build my-app --buildpack paketo-buildpacks/nodejs --builder paketobuildpacks/builder:base?

@natalieparellano
Copy link
Member

Potentially related to: https://cloud-native.slack.com/archives/C033DV8D9FB/p1669661365879809

@githubcdr could you please also provide your pack info and docker info?

@natalieparellano
Copy link
Member

Potentially related to: #1519

From Slack: disabling experimental containerd image store may fix the "missing label" problem

@githubcdr
Copy link
Author

githubcdr commented Dec 1, 2022

Thanks, I will give this a try

Client:
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.9.1)
  compose: Docker Compose (Docker Inc., v2.12.2)
  dev: Docker Dev Environments (Docker Inc., v0.0.3)
  extension: Manages Docker extensions (Docker Inc., v0.2.13)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.21.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 4
 Server Version: 22.06.0-beta.0-407-g7a5cce156e.m
 Storage Driver: stargz
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 1c90a442489720eec95342e1789ee8a5e1b9536f
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.49-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 2
 Total Memory: 7.765GiB
 Name: docker-desktop
 ID: a6522f1d-0b28-48e7-aef5-217a3851a5b6
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  hubproxy.docker.internal:5000
  127.0.0.0/8
 Live Restore Enabled: false

with pack

0.27.0+git-f4f5be1.build-3382

@githubcdr
Copy link
Author

As mentioned in the other issue, it works when disabling the containerd flag in Docker on Mac!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage Issue or PR that requires contributor attention. type/bug Issue that reports an unexpected behaviour.
Projects
None yet
Development

No branches or pull requests

2 participants