4 ms·

We switched over to Garden a year ago from a local docker-compose setup for dev. Garden has definitely had its rough spots but it works most of the time and it’

We switched over to Garden a year ago from a local docker-compose setup for dev. Garden has definitely had its rough spots but it works most of the time and it’s pretty amazing when it does. Run your dev environment remote and instantly rsync file changes and hot reload services. I’ve had an M1 Mac since launch day and not missed a beat since we don’t depend on local docker.

0x008 6y ago
How is Garden different than using docker-cli with some random container runtime other than docker?
- ths 6y ago
  (Garden co-founder here) Garden supports in-cluster building, using buildkit or kaniko. This way, you don't need to have Docker or k8s running on your dev machine as you're working. It also automates the process of redeploying services and re-running tests as you're coding (since it leverages the build/deploy/test dependencies in your stack). We also provide hot reloading of running services, which brings a similarly fast feedback loop as with local dev. The idea is to have a dev environment that has the same capabilities as the CI environment, and to be able to run any/all of your tests without having to go through your CI system (which generally involves a lot more waiting).
  - darkwater 6y ago
    We already have some home-grown kubernetes dev environment in which every developer/QA can spin up all of our services in a dedicated namespace, but it's a bit tedious and spaghetti-code as it grew organically over time (from a 15 devs team to a +70 one). Garden looks like a nice alternative solution, do you think Garden Core is enough to get started? (we like to get our hands dirty)
    - ths 6y ago
      Sounds like Garden Core could be a great fit here. The motivation behind Garden was that, like you, we had built our own home-grown kubernetes dev environments, but felt like there should be a polished, general-purpose framework + tool for this sort of thing.
    - wints 6y ago
      Hi, another Gardener here. Garden Core should indeed be enough to get started. I'm trying to keep this as factual and non-pitchy as possible for the sake of providing context—the enterprise product gets you: • RBAC and secrets management (also makes it possible to control which users have access to which types of environments) • Direct integration with GitHub or GitLab, so you could trigger something to happen in Garden based on a VCS event • Automated environment cleanup (coming soon) • Support and all that
  - madarcho 6y ago
    Your site seems to target specifically teams with messy docker compose setups. Is there a simplified/supported migration or onboarding path?
johnjungles 6y ago
Can you please share a link? When I search for garden container I get gardening results lol
- holistio 6y ago
  https://garden.io https://garden.io was first result for "garden docker"
  - reaperducer 6y ago
    https://garden.io https://garden.io was first result for "garden docker" For you. Google spends a trillion dollars a year to make sure each person gets customized search results. So being sanctimonious about your "first result" only shows that you don't know how Google works.
  - johnjungles 6y ago
    For some reason I thought I shouldn’t include docker because it’s not running docker
- deleted 6y ago
  [deleted]
desmap 6y ago
Is the creation of volumes as easy and straight-forward as with docker/docker-compose?
- 10ko 6y ago
  (Garden engineer here) You can take a look at the container module type guide to get a feel for how we reason with volumes. We have a persistentVolumeClaim module type which can used by container modules and that essentially creates a k8s pvc. See more: https://docs.garden.io/guides/container-modules#mounting-volumes https://docs.garden.io/guides/container-modules#mounting-vol...
qeternity 6y ago
Replying to my own comment: I actually forgot that Garden has the ability to run locally. We only use the remote context. So basically it’s hot reload with all your services running on a beefy cluster somewhere else.

0x008 6y ago

How is Garden different than using docker-cli with some random container runtime other than docker?

ths 6y ago
(Garden co-founder here) Garden supports in-cluster building, using buildkit or kaniko. This way, you don't need to have Docker or k8s running on your dev machine as you're working. It also automates the process of redeploying services and re-running tests as you're coding (since it leverages the build/deploy/test dependencies in your stack). We also provide hot reloading of running services, which brings a similarly fast feedback loop as with local dev. The idea is to have a dev environment that has the same capabilities as the CI environment, and to be able to run any/all of your tests without having to go through your CI system (which generally involves a lot more waiting).
- darkwater 6y ago
  We already have some home-grown kubernetes dev environment in which every developer/QA can spin up all of our services in a dedicated namespace, but it's a bit tedious and spaghetti-code as it grew organically over time (from a 15 devs team to a +70 one). Garden looks like a nice alternative solution, do you think Garden Core is enough to get started? (we like to get our hands dirty)
  - ths 6y ago
    Sounds like Garden Core could be a great fit here. The motivation behind Garden was that, like you, we had built our own home-grown kubernetes dev environments, but felt like there should be a polished, general-purpose framework + tool for this sort of thing.
  - wints 6y ago
    Hi, another Gardener here. Garden Core should indeed be enough to get started. I'm trying to keep this as factual and non-pitchy as possible for the sake of providing context—the enterprise product gets you: • RBAC and secrets management (also makes it possible to control which users have access to which types of environments) • Direct integration with GitHub or GitLab, so you could trigger something to happen in Garden based on a VCS event • Automated environment cleanup (coming soon) • Support and all that
- madarcho 6y ago
  Your site seems to target specifically teams with messy docker compose setups. Is there a simplified/supported migration or onboarding path?

johnjungles 6y ago

Can you please share a link? When I search for garden container I get gardening results lol

holistio 6y ago
https://garden.io https://garden.io was first result for "garden docker"
- reaperducer 6y ago
  https://garden.io https://garden.io was first result for "garden docker" For you. Google spends a trillion dollars a year to make sure each person gets customized search results. So being sanctimonious about your "first result" only shows that you don't know how Google works.
- johnjungles 6y ago
  For some reason I thought I shouldn’t include docker because it’s not running docker
deleted 6y ago
[deleted]

desmap 6y ago

Is the creation of volumes as easy and straight-forward as with docker/docker-compose?

10ko 6y ago
(Garden engineer here) You can take a look at the container module type guide to get a feel for how we reason with volumes. We have a persistentVolumeClaim module type which can used by container modules and that essentially creates a k8s pvc. See more: https://docs.garden.io/guides/container-modules#mounting-volumes https://docs.garden.io/guides/container-modules#mounting-vol...

qeternity 6y ago

Replying to my own comment: I actually forgot that Garden has the ability to run locally. We only use the remote context. So basically it’s hot reload with all your services running on a beefy cluster somewhere else.