Cannot run the sample in Quick Start

solo-io / bumblebee

Get eBPF programs running from the cloud to the kernel in 1 line of bash

Apache License 2.0

1.26k stars 78 forks source link

Cannot run the sample in Quick Start #66

Open vincent-pli opened 2 years ago

vincent-pli commented 2 years ago

Version

dev

Linux Version

5.11.0-49-generic

Describe the bug

There is no such image in the repository. sudo bee run ghcr.io/solo-io/bumblebee/tcpconnect:$(bee version)

The tag is dev, but there is no image with such tag:

Steps to reproduce the bug

Run sudo bee run ghcr.io/solo-io/bumblebee/tcpconnect:$(bee version) after install bee

Expected Behavior

Run success

Additional Context

No response

vincent-pli commented 2 years ago

BTW, when I try to run bee build, it tell me: Unable to find image 'ghcr.io/solo-io/bumblebee/builder:dev'

I guess they are same thing.

lgadban commented 2 years ago

Did you install bee via Go? If so that would explain why it's trying to use the dev version/tag rather than a release tag.

Can you try using one of the released tags, e.g. --

sudo bee run ghcr.io/solo-io/bumblebee/tcpconnect:0.0.9

Alternatively, you could build the example yourself to a different tag locally.

elizabetht commented 2 years ago

@lgadban I am also running into the same problem while building the eBPF program.

bee build probe.c my_probe:v1
 ▀ Compiling BPF program (1s)Unable to find image 'ghcr.io/solo-io/bumblebee/builder:dev' locally
docker: Error response from daemon: manifest unknown.
See 'docker run --help'.

  ERROR   Failed to compile BPF program
Error: exit status 125
2022/02/23 22:22:35 exiting: exit status 125

How can I correct the builder image to use the released tag?

lgadban commented 2 years ago

hi @elizabetht -- apologies for the delayed response!

you can to use the -i flag to specify the builder image, so something like this should work for you:

bee build -i ghcr.io/solo-io/bumblebee/builder:0.0.10 probe.c my_probe:v1

Did you also build bee from source?