►
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
So
this
is
the
github
org
page
of
the
flat
kalino's
org.
If
you
check
out
the
pin
repository
where
you
should
report
all
issues
you
encounter
with
flatcar
and
check
the
discussions,
you
will
find
the
agenda
discussion
for
the
community
call
of
the
respective
month
and
so
that
discussion
will
be
opened
about
one
or
two
weeks
before
the
call
starts.
If
you
want
to
add
an
item,
it's
your
chance
just
comment
to
the
issue
and
we'll
pull
in
your
item.
Then
you
can
have
a
chat
with
us.
B
B
It's
just
the
three
of
us
today.
So
there
come
visitors
of
the
stream,
but
there's
no
one
from
the
community
joining
so
that'll
be
a
rather
brief
office
hours.
I
guess
newsflash
matthew.
Do
you
want
to
cover
the
the
new
releases?
Otherwise,
I
just
keep
talking
throughout
the
meeting
and
they
don't
want
no.
A
Okay,
I
can
say
something
here
so
for
this
release:
it
landed
yesterday
and
it's
a
maintenance
release
and
a
new
measure
for
alpha,
and
most
of
all,
this
release
are
patched
with
a
dirty
pipe
c
issue.
So
that's
cool
on
the
notable
change
we.
We
have
a
patch
on
the
kernel
to
fix
some
issue
with
syria
regression
we
got
on
lts
a
kernel
of
so
that's
called
true,
and
what
can
we
say?
Okay,
the
secret
day,
one
topic,
so
maybe
jeremy?
You
want
to
elaborate
on
this
on
this
sentence.
C
Yeah
so,
prior
to
these
releases,
so
this
affects
or
applies
to
alpha
and
beta
for
the
time
being
prior
to
these
releases.
If
you
wanted
to
switch
to
c
groups
v1
you
needed
to
change
grub
config
in
the
oem
partition
from
ignition
or
or
some
other
way,
but
this
required
another
reboot
after
provisioning
to
to
to
be
applied
because
ignition
runs
after
the
bootloaded.
The
bootloader
has
already
configured
the
command
line
parameters.
C
So
what
we
did
to
to
get
rid
of
that
reboot
is
we
we
implemented
a
way
for
the
for
ignition
to
to
create
a
file
and
that
file
is
etc,
flat,
car
hyphen
c
group
v1,
and
when
that
file
exists,
then
then
the
the
ram
fs
will.
C
How
should
I
put
this
delicately?
It
will
patch
the
kernel
command
line
that
that
system
dc's,
so
that
c
group
c1
is
mounted
so
this
has
been
added
to
our
switching
to
to
syndrome,
v2
documentation
or
switching
con
c
groups,
documentation
and
flat
card
docs,
so
check
it
out.
It's
also
called
out
in
the
release,
notes,
yeah,
and
so
this
this
should
allow
people
that
need
to
stay
on
legacy
groups
to
to
do
so
without
having
to
reboot.
C
And
I
also
wanted
to
say
one
more
thing
to
the
to
the
releases
section.
So
if
I'm
not
mistaken,
we
already
have
the
releases
online
in
the
update,
server
and
aws.
I
think
it.
C
A
while
until
it
shows
up
in
azure,
but
I
think
the
mirrors
are
updated
as
well
so
for
for
fresh
deployments
but
yeah
the
releases
are
all
live
and
will
trickle
trickle
down
into
the
into
the
different
sources
in
the
coming.
I
don't
know
hours
right
tito.
You
want
to
continue.
B
Yeah,
thank
you
both
and
hi
scion.
Thanks
for
joining.
C
B
You
very
much
absolutely
thanks
folks,
and
we
had
a
dog's
writing
day
on
last
friday.
That
was
pretty
exciting.
We
had
a
hour-long
live
stream
of
people
staring
at
docs.
It
was
nice,
we
had
elf
area,
we
had
11
prs
open
it,
and
ten
of
them
are
already
merged.
B
Among
other
things,
we
fixed
a
lot
of
links
that
were
broken.
We
updated
some
of
the
examples
to
be
more
more
realistic,
more
user-centered,
and
we
have
a
new
getting
started
section
which
really
starts
from
from
zero
and
is
based
on
feedback
that
we
that
we
had
from
users
and
frequently
asked
questions
that
we
had
from
users
as
well.
B
Now,
coming
to
the
spotlight
section,
the
flag
campaigners
team
has
been
doing
a
little
bit
of
a
review
and
planning
in
the
last
two
months.
Try
to
identify
fields
and
areas
in
the
flicker
project.
They
would
like
to
work
on
also
fields
and
areas
that
need
some
work
and
a
lot
of
automation,
ideas
came
up.
A
number
of
new
features
came
up
and
we'd
like
to
use
today's
meeting
to
share
what
the
maintainers
team
is
planning
to
do.
B
B
So
the
roadmap
project
is
open
for
everybody.
So
if
you
see
a
larger
item,
a
larger
thing
that
flat
car
should
include-
and
you
want
to
discuss
it-
please
feel
free
to
file
a
respective
issue
to
start
a
discussion
and
or
to
just
join
the
community
call
and
have
a
chat
about
it
with
us.
B
For
the
time
being,
the
team
identified
a
number
of
items
just
to
give
you
an
overview
they'll
be
looking
into
using
suse
x.
Then
flat
card
system
uses
x
is
a
relatively
new
system
that
allows
for
a
layered.
B
Stack
of
system
extensions-
and
that
is
ideal
for
use
for
image
based
distros,
so
we're
going
to
replace
the
legacy,
torx
mechanism
of
picking
docker
versions
and
providing
custom,
docker
versions
and
we'll
replace
some
systemd
we'll
have
the
will
be
looking
into
oem
updates.
So
the
vendor
tools,
oem
tools
up
to
now,
don't
have
an
update
mechanism.
That
means
they
will
stay
at
the
version
that
this
respective
flat
car
instance
has
been
provisioned
with.
B
We
are
building
that
with
systemd6.
Then
we're
very
excited
about
that,
because
we
got
a
lot
of
feedback
and
it
is
sufficiently
complex
to
implement.
A
For
his
roblox
yeah
for
this
one,
not
by
them
the
id,
the
main
idea
is
to
give
some
love
to
a
flatter
test.
Suite
so
of
the
operating
system,
so
basically
improve
the
documentation
around
mental
around
collar.
How
to
run
tests
for
the
right
test,
how
to
maintain
the
old
framework
and
also
try
to
decrease
the
overall
run
time
of
the
testing
process,
because
currently
it
takes
quite
some
time
on
some
cloud
provider
so
try
to
implement
some
strategies
in
order
to
decrease
the
runtime
of
the
test
and
yeah.
A
It's
a
bit
yeah,
let's
see
how
it
goes,
but.
B
That
would
be
lovely,
yeah
cool.
Thank
you,
matthew.
All
right,
cyan,
I
see
you
joined.
Can
you
tell
us
a
little
bit
about
your
old
map
item.
D
Yeah
sure
so
yeah
so
right
now
the
release
that
we
do
is
primarily
done
a
lot
part.
A
lot
of
parts
of
those
release
pipeline
is
manual,
and
one
of
the
major
goals
of
this
whole
roadmap
item
is
to
make
the
parts
as
automated
as
possible.
So
we
will
be
working
on
automatic
the
pipeline
into
an
and
then
one
of
even
today,
I
saw
one
of
the
during
the
discussion
on
matrix
that
the
prs
and
stuff
like
we,
the
maintainers,
actually
triggered
the
ci
pipeline.
D
D
B
B
B
C
Hi
hi
sure
thing:
can
you
click
on
the
issue?
Absolutely
thanks.
So
something
I
have
been
looking
at
is
how
to
in
improve
our
security
posture,
and
so
I
will
be
looking
at
how
how
we
can
move
flat
card
to
supporting
tpm
2.0
and
in
in
practical
terms.
What
this
will
result
in
is
that
flat
car
as
a
distro
will
support
secure
boot
and
enrolling
encryption
keys
for
full
disk
encryption
in
in
a
tpm.
So
in
a
hardware-backed.
C
Storage,
and
so
there
are
several
several
things
that
need
to
be
tackled
for
that
to
work.
So
there's
work
on
upgrading
some
boot
related
packages
that
have
been
a
bit
neglected
on
our
side
ignition.
It
depends
on
on
having
ignition
v3
support,
because
the
the
third
revision
of
ignition
supports
lux
and
and
crypt
setup.
C
Yeah
and
the
rest
is
pretty
much
on
our
signing
site,
so
we
will
need
to
have
secure
signing
infrastructure.
For
the
I
mean
we
already
have
signing
for
for
a
lot
of
the
artifacts,
but
there
are
certain
additional
requirements
to
to
get
our
bootloader
signed
with
the
secure
boot
ca
and
then
and
then
certified
so
yeah.
That's
a
it's
an
exact,
exciting
roadmap
item
and-
and
I
look
forward
to
the
features
trickling
into
releases
in
the
next
month-.
B
Me
too,
thank
you
all
right,
I'll
cover
credit
in
this
item
because
he's
not
around
as
a
credit,
as
I
covered
kai's
item
so
guys,
focusing
on
the
physics
stuff
question
mirror
has
been
working
hard
under
the
in
the
machine
room,
updating
packages
and
updating,
e-classes
and
making
things
more
aligned
with
gen
gen2
everybody
who
doesn't
know
we're
using
two
e-build
repositories.
The
first
is
chorus
overlay,
which
is
kind
of
specific
to
flat
car
and
the
other
is
portage
stable.
B
You
can
find
it
by
just
going
to
a
flatcut
container
linux
and
then
the
github
org
and
then
check
the
project
section,
and
then
you
will
see
the
roadmap
if
you
think
that
there
is
something
missing
here,
if
you
feel
that
if
you,
if
you
have,
if
you
feel
an
initiative
to
contribute
to
any
of
the
rope
items
on
this
board,
either
you've
discussed
them
today
or
we
didn't,
please
feel
free
to
reach
out
to
us
if
you
want
to
propose
your
own
direction.
B
B
Okay,
I
right,
if
you
want
to
oh
there,
he
is
just
just
in
time
cyan.
Would
you
like
me
to
share
the
release
board,
or
would
you
like
to
share
yourself.
D
Okay,
I'll
try
to
speak
out
loud.
I
can't
cough
so
maybe
because
of
that
yeah.
So
so
we
are
in
between
a
release.
D
We
just
completed
the
release
yesterday,
so
this
was
slipped
by
a
week,
so
we,
I
did
not
start
planning
the
next
one
that
would
probably
come
after
the
community,
so
we
would
see
a
gap
again
for
the
three
weeks
but
anyway
so
and
we
had
we
decided
on
on
me
on
the
release
channel,
that
we
shift
the
existing
14
march
release
to
24th
1st
of
march
release.
So
for
the
next
cycle.
We
are
starting
to
work
on
it
and
we
have
a
couple
of
so.
D
I
would
see
I
would
say
the
major
focus
would
be
around
the
packages
which
would
have
a
couple
of
upgrades
in
in
them
so
yeah,
and
if
you
cannot
look
into
that,
that
will
probably
slip
into
the
next
one.
But
for
now
we
are
looking
into
the
backlog
one
and,
as
as
mentioned,
we
have
four
contributors
looking
into
looking
to
contribute.
D
Tria
section
is
a
good
way
to
look
into
because
these
these
are
the
packages
which
would
need
a
bit
of
digging
on
how
basically,
what
needs
to
be
done.
So,
if
you
are
interested
triage,
is
the
best
section
to
look
into
and
if
you
are
already
doing
package
maintenance,
then
the
triage
as
well
as
you
can
look
into
backlog,
but
yeah,
that's
mostly
like,
I
would
say
it
would
be.
A
package
upgrade
heavy
release.
Next
one,
the
next
one.
D
Yeah
so
another
thing
I
wanted
to
mention
peter,
so
I
added
my
roadmap
item
and
the
idea
which
I
was
thinking
was.
D
So
the
idea
that
I
was
thinking
was
that
in
the
road
in
the
blocked
or
long
term
items,
we
could
just
give
an
update
of
how
things
are
looking
from
the
roadmap
item
set
so
from
the
next
release.
If
you
think
that
would
be
good.
B
That's
not
a
bad
idea
yeah,
so
to
provide
even
more
background
on
that.
We've
been
splitting
down
those
roadmap
items
into
into
more
more
tangible
tasks
which
we're
going
to
plan
in
the
metrics
channel
starting
next
week,
and
we
could
actually
check
those
off
in
the
in
the
release
planning
as
well.
That
makes
a
lot
of
sense.