kelda / blimp Goto Github PK

What happened?

❯ blimp up
Booting cloud sandbox
[Error] Get help at https://kelda.io/blimp/docs/help/
Message: Failed to create development sandbox
Error: rpc error: code = Unavailable desc = transport is closing

The buildkit pod is unhealthy, with the following logs:

time="2020-12-21T04:38:58Z" level=warning msg="/proc/sys/kernel/unprivileged_userns_clone needs to be set to 1."
[rootlesskit:parent] error: failed to start the child: fork/exec /proc/self/exe: operation not permitted

What were you expecting to happen?

Buildkit should successfully start, and the development sandbox should be deployed.

There's some additional UX issues here as well:

• The error message should be better.
• The compose file doesn't even require building images. So even if buildkit isn't working, we should let the development sandbox be created.

Reproduction steps

Additional context

Switching to non-rootless images for buildkit may fix the issue on DO.

Reported by Ian Walter in Slack (https://kelda.slack.com/archives/C4LF0KL4D/p1608525499118200)

Is your feature request related to a problem? Please describe.
We have many environment initialization routines implemented inside the docker image and run with compose (e.g. docker-compose run backend load_db). In order to completely replace docker-compose with blimp, it would be nice that blimp supports that syntax and behaviour.

Describe the solution you'd like
Be able to blimp run backend load_db (with or without support for the other parameters).

Additional context

$ blimp run backend load_db
unknown command "run" for "blimp"

Did you mean this?
	up

PS: I just found this project and looks really promising. Thanks!

Nice product you have here 👍 . Here is some feedback from my personal use:

Is your feature request related to a problem? Please describe.
When user accidentally include build command on docker-compose.yml e.g. step to reproduce:

1. Clone the official example git clone https://github.com/kelda/node-todo && cd node-todo
2. Edit docker-compose.yml, include a build command, like this:

version: '3'
services:
  web:
    # for example I accidentally include build command here:
    build: .
    entrypoint:
      - "/usr/src/app/node_modules/.bin/nodemon"
      - "/usr/src/app/server.js"
    ports:
      - "8080:8080"
    depends_on:
      - mongo
    volumes:
      - "./app:/usr/src/app/app"
  mongo:
    image: "mongo"
    ports:
      - "27017:27017"

3. save the file
4. run blimp up

User will get the following error message which might not be descriptive enough for user to fix the issue:

➜  node-todo git:(master) ✗ blimp up
Booting cloud sandbox
Building image for web:
[Error] Get help at https://kelda.io/blimp/docs/help/
build web: start build: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Describe the solution you'd like

• Catch that error message, and tell user to not avoid docker build command in the docker-compose.yml file.
  OR
• read the docker-compose.yml file and if build command is detected, refuse to run and display proper err msg.

or maybe somekind of messaging looks like you are trying to invoke Docker 'build' command, this command is not currently supported in Blimp's cloud container. Please check your 'docker-compose.yml' file and remove the 'build' command.

Additional context
User can easily accidentally include build command within docker-compose.yml because they think Blimp is ready-to-use drop-in-replacement for Docker Compose (as you describe it). And lots of users are having build command within their docker-compose.yml.

If they run blimp up and it didn't work, they may think your product is broken or not working as described. They may drop off. So this will be good improvement for new user who might not understand anything of your product.

Well it took me a while to figure out what went wrong too.

Is your feature request related to a problem? Please describe.
In order to specify different docker-compose.yml files, it would be nice that blimp supports the environment variables that docker-compose uses, specifically the COMPOSE_FILE environment variable.

Describe the solution you'd like
When the COMPOSE_FILE environment variable is set, blimp uses it to find the Compose file(s).
This probably also implies adding support for multiple Compose files, because COMPOSE_FILE may specify many files concatenated with :.

Additional context
Probably adding CLI support would be nice too (docker-compose -f file.yaml).