►
From YouTube: Flatcar Container Linux community meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
This
is
the
april
call.
We
have
a
few
bits
and
pieces
prepared
for
you
folks,
so
maybe
we
start
with
sharing
the
agenda.
A
B
B
F
Sure
yeah,
no,
I
I
am
just
a
fly
on
the
wall
this
week.
My
name
is
tony
gosselin.
I
am
a
an
engineer
over
at
adobe
we
are
a
consumer
of
flat
car,
big
fans
and
we
are
looking
to
be
more
on
the
the
front
end
of
the
the
release
schedule.
So
I'm
here
to
see
what's
coming
up.
B
Cool
yeah,
we
have
something
for
you
later
on,
then
I
guess:
release
planning
is
always
a
part
of
this
of
this
community
called
and
thanks
for
joining,
actually
you've
been
providing
very
valuable
feedback
in
the
in
the
last
weeks
and
months
always
happy
to
have
you
all.
B
You're
welcome
all
right,
so
that's
the
hello
on
just
making
sure
I
don't
forget
anyone
else.
Oh,
that
seems
to
be
it
all
right.
Thanks
for
saying
hi,
we
have
a
number
of
news
items.
First,
the
we
have
a
bunch
of
releases
that
went
out
last
week
more
not
in
the
release
planning
part
later
on
the
most
important
part,
or
at
least
a
major
news
item
is
that
kernel
515
then.
B
Basically,
the
current
lts
kernel
has
gone
stable
and
is
available
through
the
stable
channel
now
and
the
next
news
item,
which
is
in
preparation.
So
it's
not
available
yet,
but
we're
looking
into
that
we're
working
on
a
new
lts
release
and
formally
lts
was
only
available
to
subscription
customers.
Since
we
were
acquired
by
microsoft,
we're
now
able
to
publish
lts
as
a
community
release,
so
everybody
will
benefit
on
that
users
of
the
old
lts
will
remain
on
the
old
lts.
B
All
right,
so
that's
for
the
for
the
news.
Let's
switch
to
spotlight,
I
stopped
sharing
my
screen
and
you
forks
can
have
your
full
attention
and
we'll
start
with
the
ignition
afterburn
and
butane
work.
C
Yes,
thanks
todo
for
the
introduction
so
recently
in
the
latest
alpha
and
beta,
we
upgraded
the
ignition
so
we're
now
able
to
support
ignition
v3
and
ignition
v2
configuration.
So
this
is
really
cool.
It
was
long
time
we
were
still
on
the
v2
version.
So
now
we
support
both
versions
and
we
also
added
the
ability
to
generate
ignition
d3
using
butane.
E
Sure
happy
too
yeah
so
butane.
This
was
built
as
a
successor
to
to
ct
and
it
has
the
same
goals
and
then
we
also
based
some
changes
on
our
experience
with
ct
some
things
that
we
wanted
to
fix.
E
So
just
as
a
reminder,
goals
that
we
inherited
from
ct.
We
want
to
provide
a
human
friendly
syntax
to
as
a
front
end
to
ignition
right
ignition
is
json,
it's
a
little
hard
to
to
handwrite
it's
possible,
but
we
don't
recommend
it.
So
we
provide
a
yaml
version
of
that
syntax.
E
First
of
all,
then
we
provide
additional
validation
services.
So,
ideally,
if
you
write
a
config
and
there's
something
wrong
with
it,
you
wouldn't
have
to
actually
boot
a
machine
with
it
to
see
that
it
didn't
work
to
the
extent
possible.
It
would
be
nice
to
validate
that
config
before
putting
it
in
user
data
somewhere
and
ct,
and
now
butane
have
the
ability
to
have
those
validations
and
then
the
last
thing
is
sugar.
E
E
We
have
sugar
in
in
butane
that
lets
you
configure
raid
on
the
fedora
core
s
and
rel
core
s.
Side
configure
boot
disk
raid
for
your
system
with
this
fairly
small
amount
of
syntax.
E
So
what
that
is
is
just
higher
level.
Syntax!
That's
for
this
service,
configure
this
option.
We
call
that
sugar.
E
In
addition,
as
I
said,
we
wanted
to
fix
a
couple
things
from
from
ct
and
one
of
those
the
big
one
is
that
if
you
look
at
a
container
linux
config,
you
can't
really
tell
what
version
of
ct
it's
intended
to
be
run
with.
You
have
to
like
recognize
certain
config
fields
that
were
added
in
this
particular
version
of
ct.
That
kind
of
thing,
and
that
wasn't
ideal.
I
think
we
had
a
recommendation
at
one
point
that
you
checked
the
ct
binary
into
your
version
control
system.
E
It
just
didn't
work
that
well
so
butane
configs
have
a
version
number
embedded
in
them.
You
can
look
at
the
config
and
know
exactly
what
directives
will
be
supported
and
also
you
can
know
exactly
what
version
of
the
ignition
spec
will
be
emitted
when
you
transpile
that
config
and
that
matters
during
an
ignition
spec
transition,
maybe
you're
working
with
older
os
versions
that
don't
support
the
new
config
yet
and
you
can
avoid
accidentally
generating
configs
that
won't
boot.
E
That's
the
one
thing
and
then
the
other
thing
is
distro
independence.
So
butane
was
consciously
written
to
support
multiple
linux
distros
that
might
use
the
ignition
it's
there's
a
there's,
a
subclass
hierarchy.
Essentially,
so,
in
addition
to
config
version,
you
write
what
we
call
the
variant,
so
variance
right
now
might
be
f,
cos
open
shift
and
we
just
merge
a
flat
variant
and
the
it's
a
variant
version
pair.
So
each
variant
is
independently
versioned.
E
It
inherits
from
a
particular
base,
which
is
generic
support
for
ignition
configs
of
a
particular
spec.
A
base
might
have
some
sugar,
that's
common
to
all
variants
like
the
ability
to
to
inline
local
files
from
the
file
system.
For
example.
That's
useful,
no
matter
what
distro
you're
running
so
the
base
might
have
sugar
and
then
the
variant
might
have
additional
sugar.
That
is,
that
provides
support
for
specific
services.
E
E
E
E
I
think.
That's
all
I've
got
I'll.
Just
mention
again
prs
are
welcome.
We're
happy
to
to
take
additional
support
for
additional
things,
happy
to
take
bug,
fixes
and
yeah
any
questions.
C
Okay,
so
I
will
follow
with
a
quick
demo.
It
will
illustrate
just
what
you
mentioned
about
the
version
variant
and
so
on.
So
I'm
about
to
share
my
screen.
Everyone
should
see
my
screen
and
if
there
is
an
issue,
just
let
me
know
so,
I
have
this
config.
So
it's
a
really
simple
complaint.
The
objective
is
to
be
able
to
encrypt
the
device
using
linux.
C
We
can
see
the
version
that
benjamin
mentioned,
so
in
this
case
it's
1.0.0
and
it
will
generate
ignition
version
3.3.0
exactly
and
if
we
want
to,
we
can
precise
the
over
version
like,
for
example,
if
you
live
on
the
edge
and
you
want
to
try
out
some
experimental
stuff,
you
can
just
mention
the
experimental
version
and
also
you
have
the
variant
in
this
case.
It's
black
fatca.
C
So
one
cool
thing
with
this
with
this
simple
configuration-
is
that,
for
example,
on
the
last
line,
we
have
the
with
mount
unit
section
and
this
section
will
will
tell
to
be
claimed
to
generate
some
files
in
order
to
automatically
mount
the
the
created
lux
device
into
the
the
specified
path
into
the
file
system
section.
So
this
is
very
interesting
because
you
try
to
keep
your
configuration
simple
and
retain
try
to
take
care
of
the
rest.
C
C
I
can
see
in
my
file
that
there
is
a
systemd
unit
that
has
been
autogenerated
by
butane,
so
this
is
the
one
I
mentioned
earlier.
It
is
about
to
mount
things
in
the
right
place,
and
now
we
can
easily
boost
a
flat
car
instance
and
to
see
that
it
works
correctly.
So
the
instance
is
already
booted,
I'm
just
about
to
ssi
chain
gen2,
and
we
can.
C
We
can
check
quickly
that
the
bd4
is
currently
encrypted
with
flux
and
we
have
the
it's
for
system
type,
creating
of
the
data
and
it's
being
mounted
on
valid
data.
So
it
works
as
expected,
and
if
we
check.
C
So
this
is
quite
cool
because,
as
I
said,
you
can
keep
things
really
simple,
but
of
course
you
can
supply
your
own
key
if
you
want
to
and
it
will
be
served
by
http,
https,
server
or
s3
or
whatever
you
want,
and
also
it
will
generate
this
crypt
tab
configuration
so
like
so
every
time
you
will
reboot
the
instance,
it
will
work
as
expected.
H
We
now
have
something
that
allows
you
to
extend
the
slash
user
directory
or
higher
actually
when
overlay-
and
this
perfectly
fits,
for
example,
the
use
case
of
custom
docker
container
d
as
well,
and
therefore
we
will
duplicate
talks
and
yeah.
We
just
want
to
share
that.
We
have
docs
in
the
provisioning
section
of
the
fed
catalogues
and
some
heifer
tools
to
create
systemd,
susex
images
from
upstream
docker
releases
or
old
talks
images.
B
H
Yeah,
so
it's
not
yet
implemented,
but
the
idea
is
that,
for
example,
docker
would
be
still
shipped
on
like
this
flat
car,
but
as
a
enables
this,
the
6x
images
is
enabled
by
default.
So
that
allows
you
to
easily
disable
it.
If
you
don't
need
it
for,
because
you
have
your
own
docker
version,
you
want
to
provision
and
later
on,
yeah,
or
maybe
you
don't
want
to
use
stock
at
all
or
you
have
something
else
to
use
as
a
content
container
runtime
and
later
on.
H
We
also
plan
to
use
this
for
the
purposes
of
the
rem
partition.
That's
we
are
currently
very
limited
so
that
we
can
have
something
that
gets
an
atomic
updatable
image.
H
B
B
B
Yes,
please
only
one
window,
that's
better,
okay,
so
we're
making
use
of
the
new
github
projects
2.0
boards,
which
are
currently
in
beta
and
iteratively,
extended
with
new
features,
and
that
allows
you
to
have
multiple
views
on
a
set
of
issues
and
since
the
issues
in
our
main
flat,
car
project
have
become
quite
a
lot.
So
we're
doing
long-term
planning,
short-term
planning,
back
tracking
and
even
events
planning
with
those
issues.
It
actually
pays
to
have
different
views
on
things.
B
B
We
have
our
releases
board,
which
is
now
just
the
view
on
the
on
the
overall
board,
which
will
look
into
more
detail
in
a
minute
when
we're
doing
release
planning
and
that
reuses
all
of
the
stuff
that
went
through
the
tactical
board,
so
it
goes
hand
in
hand.
We
have
a
roadmap
board
that
was
formerly
a
separate
project,
and
roadmap
tracking
involves
epic
issues
that
are
split
down
into
multiple.
B
Then
there
is
line,
work
items
line,
worker
stuff
that
is
not
connected
to
any
epic,
maybe
bugs,
maybe
maybe
smaller
tasks
or
smaller
endeavors
that
that
they're
looking
into
and
lastly,
who
does
what
this
year,
that's
basically
a
board
that
shows
active
persons
that
have
issues
assigned
and
what
issues
they
have
assigned,
and
this
is
the
main
view.
That's
what
we're
mostly
looking
at
and
with
that
I'll
conclude
this,
please
have
a
look
share.
I
Yeah,
as
they
mentioned
like,
we
have
moved
to
a
new
board
so
releases
we
are,
we
are
have
already
deprecated
the
older
release
board
and
we
going
forward.
We
would
be
using
the
this
tactical
replacement
or
the
github
boards,
and
so
before,
starting
off
so
right
now,
one
of
the
focusing
that
the
team
has
been
working
on
has
been
around
the
build
and
release
automation.
I
So
you
will
see
a
lot
of
ci
automation,
work
in
progress
and
a
bunch
of
them
are
in
the
planned
item,
so
the
team
would
be
taking
taking
up
the
items
in
the
next
week
or
so
so.
So
I
wanted
to
know
like
in
around
this,
like
a
lot
of
folks
won't
be
available
next
week
and
in
india.
Also,
we
are
having
holidays
this
week
so
and
I
will
be
also
be
able
to
like.
I
I
will
be
gone
on
the
last
week
of
april,
so
I
was
wondering
if
you
could
switch
the
release
to
the
second
of
may,
instead
of
the
24th
of
april
release.
How
does
that
sound.
I
And
so
kai
we
would
be
doing
the
2022
lts
release
in
the
on
the
fifth
of
main.
That
sounds
good
right.
I
Right,
okay,
cool,
so
keeping
it
as
a
light
week.
So
I
know
lsu
will
be
gone
next
week
yeah.
I
guess
so.
He
has
been
working
on
the
live
like
stuffs
and
probably
next
week.
I'll
continue
with
picking
up
from
the
focus
item,
which
is
the
automation
stuff,
so
we'll
probably
keep
the
load
of
the
number
of
packages
that
mars
low
and
the
regular
as
we
would
keep
on
merging
the
linux
kernel,
pr's
and
but
other
than
that.
I
The
package
maintenance
would
be
prs
that
get
much
would
be
low
and
it
would
be
a
pretty
night
release,
even
though
we
are
extending
the
time
it's
just
because
of
the
absence
around
the
team
over
the
next
three
weeks,
and
so,
okay,
so
yeah.
So
I
guess
over
the
next
weeks
we
would
see
the
cia
automation
works,
getting
completed
right
and
more
of
those.
These
vendors
are
also
getting
completed
over
the
next
three
weeks.
B
Definitely
keeping
fingers
crossed
for
that
one.
Yes,
that's
I
have.
I
have
high
hopes.
We
have
a
lot
of
traction-
it's
not
really
tangible
in
terms
of
having
new
stuff
in
the
os
image,
but
it'll
it'll
make
building
and
testing
and
building
test
automation
so
much
easier.
So
I
really
look
forward
to
that.
I
Cool
okay,
so
in
that
case,
yeah
as
discussed,
we'll
keep
the
release
light
and
let's
focus
on
getting
more
of
the
automation
done
here
and
yeah.
G
I
have
something
it's
related
to
some
of
the
the
pro
elements
of
flat
card
that
recently
made
their
way
to
the
the
beta
channel,
so
the
nvidia
driver
bring
up
on
on
boot.
I
know
there
are
some
some
some
folks
in
the
community
who
do
things
differently
and
I'm
also
looking
into
collaborating
with
nvidia
to
get
their
driver
container
solution
working.
G
If
anyone
wants
to
wants
to
collab
on
that
or
has
any
suggestions
for
or
experiences
on
how
how
this
could
be
improved,
then
reach
out
and
we'll
see
what
we
can
do
together.
I
Sure
yeah
thanks
jeremy,
so
we
could
probably
even
create
an
issue
around
that.
It's
been
long
that
we
walked
around
the
whole
nvidia
thing
and
got
to
have
the
work
that
you
have
been
doing.
B
This,
of
course,
also
touches
issues
that
you
that
you
would
like
to
raise
or
features.
You
would
like
us
to
work
on,
so
you
could
put
stuff
on
our
plate.
You
are
users
and
what
you
need
is
most
important
to
us,
but
I
really
look
forward
to
the
to
the
gpu
stuff
as
well.
Oh,
which
reminds
me
we
had
an
experimental,
I
wouldn't
even
say
change,
but
we
had
something
in
the
in
the
works
that
would
solve
some
of
the
oem's
python
dependencies.
I
don't
know
how
far
that
has
gotten
jeremy.
G
Well,
I'm
gonna,
I'm
gonna
pitch
the
solution
that
I
that
I
found
and
see
what
the
feedback
from
the
rest
of
the
team
is.
So
basically,
there
are
various
projects
around
github
that
build
a
or
pre-build
a
standalone
self-contained
python
install
with
all
the
dependencies.
Most
importantly
openssl.
G
The
issue
we
have
right
now
is
since
our
oem
partition
is
not
updated
relative
to
the
os.
We
need
to
keep
it
decoupled,
so
we
can't
really
link
to
anything
in
the
in
the
os,
and
so
this
was
a
solution
to
kind
of
keep,
keep
maintenance
overhead
low
for
us
and
and
have
have
something
that
that
works
well
enough
on
so
so,
primarily
for
for
azure,
where
azure
requires
a
full
python
install
to
support
the
many
vm
extensions
that
that
that
can
be
installed
onto
onto
virtual
machines.
G
We
know
that
this
enables
at
least
a
vm
backup
or
vm
snapshot
extension
to
run,
hopefully
more
use
cases,
work,
yeah
and
size
wise.
This
works,
so
it
fits
on
the
oem
partition
using
more
or
less
the
same,
maybe
slightly
more
space
than
than
we
currently
consume,
but
there's
still
plenty
left
over.
G
So
I'm
gonna,
I'm
gonna
open
up
pr
soonish.
I
I
don't
expect
any
quick
feedback
due
to
easter,
but
if
someone
has
any
thoughts
on
on
how
the
solution
would
work
for
them,
then
I
might
be
glad
to
see
hear
some
amazing
yeah.
That
sounds
great.
B
B
All
right
yeah,
I
I
wish
we
had
something
like
that
lined
up,
but
it's
actually
it's
a
it's
a
very
good
point.
So
if
you
want
to
meet
some
of
us
in
person,
we
will
be
around
kubecon
in
valencia
I'll
be
there.
Some
from
the
team
will
be
there
and
we,
of
course,
will
be
there
for
rejects,
which
happens
on
the
weekend
before
kubecon,
so
yeah.
If
you
want
to
hang
up,
if
you
want
to
hang
out,
then
absolutely
we'll
we'll
we'll
be
around.
B
B
Flat
car
I'm
support
for
aks
the
arm
better
for
aks
just
launched
with
ubuntu
and
senders
yeah.
That
is
correct
and
we've
been
looking
into
that
and
the
last
step
that
is
missing.
So
everything
works
first,
first
things
first
and
we
even
managed
to
improve
some
general
operations
of
flatcon
as
a
in
the
process
while
onboarding
there.
B
B
We
have
a
third
party,
not
a
first-party
market,
place
offering
on
azure
and
we're
in
discussion
of
onboarding
dart
to
to
the
arm
64
offering
on
azure,
while
we
don't
have
any
timeline
or
announcements.
Yet
we
have
high
hopes
that
flat
covers
soon
be
available
on
arm
64
on
azure,
and
I
mean
the
the
arm.
64
team
also
has
those
expectations.
That's
why
they
called
us
out
in
their
in
their
announcement.
G
Just
one
thing
to
add:
tilo,
you
were
talking
about
the
flat
car
arm,
support
for
azure
general
right,
not
aks,
specifically
so.
H
G
Out
of
out
of
scope,
I
think
that's.
B
B
I
I
misread
we
do
have
yeah,
that's
that's
probably
the
next
step.
Then
that's
actually
a
good.
A
good
call
out.
F
Okay,
no,
that's
that's
good
to
know
cool!
That's
one
of
the
the
many
things
we've
been
pursuing
on
our
end
here,
so
I'll.
Let
the
arm
folks
know
on
our
end
that
it's
it's
coming
to
azure
student
and
then
aks
after
that.
B
F
B
Can
I
bug
you
tony
to
set
up
to
to
just
file
a
feature
request,
so
we
can
track
it
in
the
project
that
will
be
valuable,
yeah
we'll
do.
J
Awesome
just
clarifying
so
you're
saying:
there's
no
support
for
aks
and
for
us
to
make
over
a
feature
or
issue
request
for
this.
Yes,.
B
We
I'm
actually
unsure
this.
Is
this
is
kind
of
undiscovered
country,
so
I
would
need
to
look
into
that
and
what
ubuntu
and
centers
are
doing
there
and
what
is
necessary
for
flat
car
and
then
follow
up
a
few
folks.
I
misread
the
the
chat
statement
and
I
thought
it
was
about
general
azure.
J
Okay,
now
fair
enough,
I'm
actually
meeting
with
the
broader
azure
team
as
well,
so
I'll
also
bring
it
up
with
our
counterparts
who
are
working
with
us
for
our
aks
migration.
G
H
G
We've
developed
and
are
pretty
much
just
blocked
on
publishing,
so
that
would
be
coming
to
arm
64
as
well.
J
Very
interesting
jeremy
because,
like
I,
was
just
talking
to
lockheed
evanson
from
microsoft,
about
just
overall
cap
z,
so
we
definitely
would
love
to
find
out
more
about
this.
B
All
right
the
most
excitement
at
the
end
of
the
call.
I
really
like
it
all
right
folks.
Anyone
has
any
any
questions
or
feedback
for
us.
This
is
what
we're
here
for.
B
Calling
once
calling
twice
all
right,
thank
you
all
for
attending
thanks
for
the
great
input.
B
This
is
gaining
some
traction
and
I
feel
it
and
it's
it's
great
to
have
you
here
and
thanks
benjamin
for
for
the
for
the
great
intro
for
boutain,
we'll
make
sure
to
do
lots
more
upstream
work
in
the
in
the
future.
That's
what
our
our
main
focus
is.
All
right,
yeah
see
you
maybe
in
two
weeks
and
already
is
planning
or
in
a
month
for
the
next
community
call
and
until
then
maybe
visit
us
on
metrics
or
look
into
the
project
and
github
thanks
see
you
thank
you.