Re: Debian Buster container inside AWS ec2

[Cauã Siqueira <caua.siqueira@protonmail.com>]

With CoreOS its working beginning (below).

#cloud-config

coreos:
  units:
    - name: update-engine.service
      command: stop

    - name: "copy-cert.service"
      command: "start"

But, to Debian i cannot found an option to build units.

Cauã.



Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, May 18, 2020 12:19 PM, Noah Meyerhans <noahm@debian.org> wrote:

> On Mon, May 18, 2020 at 02:59:50AM +0000, Cauã Siqueira wrote:
>
> > My name's Cauã (Brazilian) and i use Debian for many years. I'm building a new infrastructure inside AWS with terraform. We're migrating from CoreOS to Debian (choice me), but we're having a problem with userdata to create systemd with others containers to running inside Debian Buster (https://wiki.debian.org/Cloud/AmazonEC2Image/Buster).
> > See below a little example about my userdata. I can't found docs to help me. Could you help me, please ?
>
> Cloud-init documentation is athttps://cloudinit.readthedocs.io/en/18.3/
>
> > systemd:
> >
> > -   name: "filebeat.service"
> >     command: "start"
> >     contents: |
> >
>
> ...
>
> This isn't valid cloud-init cloud-config data. Cloud-init doesn't have
> a "systemd" module. You mentioned that you are migrating from CoreOS.
> Is this something that worked with Ignition? If so, it looks like you
> have more porting work to do. Cloud-init's write_files and runcmd
> modules would appear to be useful here.
>
> noah