►
From YouTube: Flatcar Container Linux community meeting 2022-01-11
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).
A
C
C
And
here
we
go
all
right
folks.
This
is
the
first
meeting
in
2022.
Many
of
us
have
enjoyed
the
time
off
so
in
the
meeting
today,
we're
going
to
share
a
little
bit
of
an
overview
of
what
we
did
in
2021
and
start
to
give
you
an
idea
of
things
to
come.
C
The
more
significant
meeting
for
the
things
to
come
will
be
the
february
meeting,
though
we
are
currently
working
on
plans
for
flat
car
that
the
maintainer
team
here
wants
to
see
happen
and
we'll
share
that
with
you
in
the
next
meeting.
If
you
have
your
own
plans
with
flat
car,
please
join
and
share
work
with
us.
C
Detour
to
flat
count
raspberry
pi,
which
is
some
great
work
that
zion
and
that
cyan
did
with
work
based
on
things
that
jeremy
provided
and
we'll
have
a
deep
dive
into
fleet
lock,
and
then
the
release
planning
is
back,
which
we
didn't
do
in
december,
because
there
were
no
releases
over
the
christmas
period.
C
C
C
That's
a
significant
jump
onto
the
next
lts
kernel
that
we
will
include
and
there's
a
lot
of
updates
of
major
and
minor
operating
system
packages
you're,
particularly
working
under
the
hood
on
the
sdk
tools
and
libraries
and
there's
a
lot
of
things
to
come
there
as
well.
This
alpha
release
won't
finish
that
work,
but
it'll
be
a
significant
jump
in
the
right
direction
and
we
have
a
number
of
fosdem
talks
coming
up.
C
B
D
Maybe
for
the
next
yeah,
so
so
yeah
I'll
be
giving
a
talk
on
securing
a
hardened
container
hose,
which
is
essentially
like
these
days.
Security
is
one
of
the
major
points
in
any
deployments
that
we
do
and
flat
is
security
first
operating
system.
So
taking
all
that
into
picture.
D
C
Yeah
I'll
have
a
quick
talk
with
some
hands-on
prepared
demos
for
well,
basically
modding
flat
car
into
doing
whatever
you
want
it
to
do.
It's
an
immutable
image
by
default,
so
we'll
be
looking
into
the
flat
car
sdk
and
how
to
train
the
next
10
flat
car,
and
then
we
have
an
infrastructure
talk
that
kai
has
proposed.
We
don't
have
any
feedback
on
that
yet,
but
then
the
schedule
of
the
infrastructure,
dev
room,
hasn't
been
published,
and
I'm
thinking
for
kai
here,
because
he's
not
here
today
so
there'll-
be
a
proposed
infrastructure.
C
Talk
on
the
immutable
infrastructure
on
creating
a
with
black
car
linux,
using
one
of
the
main
features
of
the
operating
system.
If
you're,
if
you
are
accepted,
that
will
happen
in
the
infrastructure,
dev
room-
and
I
just
keep
talking
because
my
second
talk
is
in
the
container
step
room
and
that
is
about
flat
cars,
auto
update.
It
will
elaborate
in
the
specific
into
the
specifics
of
flat
cars
update
system
and
it
will
generalize
into
a
few
patterns
that
people
might
want
to
investigate
when
they're
updating
their
clusters.
C
And
coming
to
us
spotlights
quick
recap
of
2021:
we
invested
a
lot
of
effort
in
upgrading
major
system
components.
We
had
a
new
kernel
version
latest
lts
kernel.
At
that
time
we
upgraded
to
docker
20
and
system
d249,
which
allowed
us
to
switch
to
secret
v2,
and
we
once
again
upgraded
the
c
library
and
the
sdk,
as
well
as
the
operating
system
image
to
the
latest
version.
C
We
modernized
the
number
of
subsystems.
They
will
switch
to
c
groups,
v2
that
was
exciting,
jeremy
drove
that
mainly
great
work
and
we
updated
iptables
to
use
the
nav
tables
and
then
arm
64.
Finally,
then
stable
just
in
time
in
the
late
last
stable
release
of
of
2021,
and
there
was
a
lot
of
work
involved,
most
significantly,
testing
work
and
bringing
tests
back
into
shape
for
arm
and
fixing
pocket,
upgrading,
poked
and
switching
from.
I
think
it
was
spider
monkey
right,
william.
C
C
So
we
have
increased
test
coverage
on
equinix
metal,
bare
metal,
hosts
generation,
three
hosts
that
include
both
arm
64
and
intel
hosts.
C
We
regularly
test
and
support
flat
car
and
graviton
v2
gretchen
access
to
graviton
v3
is
requested
and
we're
waiting
for
aws
to
get
back
to
us
and
we're
supporting
azure
generation
two
vms,
and
we
also
test
our
releases
on
those.
C
D
Thank
you,
sorry
thank
you
and
yeah,
so
over
the
over
the
so
the
last
last
month,
or
I
should
say
the
end
of
2021,
we
had
one
of
the
biggest
exciting
news
coming
in
was
going
to
stable
and
one
of
the
really
like.
D
If
you
talk
about
arm
in
general
public
like
they
usually
people
resonate
with
raspberry
pi,
because
it's
very
widely
known
and
a
lot
of
people
have
been
using
raspberry
pi
in
their
home
labs
and
it's
not
really
like
just
developer
or
playing
around,
but
people
really
use
doing
production
level
stuff
on
on
their
homeland
on
their
private
home
lab
setup.
So
this
is
some.
D
This
is
some
work
that
jeremy
was
doing
for
a
couple
of
months
and
after
the
walk
went
into
stable
I
and
during
the
christmas
holidays,
I
thought
that
a
good
work
that
I
could
do
was
to
think
around
with
raspberry
pi,
because
I
had
a
couple
lying
around
and
then
I
ordered
a
few
more
so
you
can
see
the
picture
on
the
right,
so
I
started
tinkering
around
and
there
were
a
few
steps.
There's
a
good
documentation
there
investor.
D
If
I
talk
about
the
official
documentation-
and
so
the
first
thing
is
to
get
the
eb
rom
update,
the
reason
is,
there
are
a
few
things
that
are
supported
in
the
latest
versions
and
you
would
be
needing
those
to
get
ahead
with
the
with
the
installation.
So
so
that's
one
of
the
primary
things
you
start
off
with
and
then
the
next
thing
is
you
install
the
flat
car
on
sd
card
or
in
usb
usb
is
the
recommended
one.
D
The
reason
being
had
been
fast
and
more
durable
in
terms
of
uses.
So
you
do
this
particular
installation
via
flat
card
install.
We
have
a
flat,
install
scripts
that
you
usually
use
to
interact
with
their
metal,
so
you
can
use
that
particular
script
with
the
with
the
providing
the
image
and
it
would
install
that
but
install
flat
card
onto
the
usb
and
the
final
step
is
getting
the
uefi
firmware.
So
this
whole
step,
as
I
mentioned,
is
not
really
like.
D
The
ufi
is
not
official
one,
but
then
the
I
guess
it
was
rpi
for
ufx.
D
So
those
folks
are
working
really
doing
some
really
good
work
on
getting
a
firmware
out
and
the
work
that
they
have
been
do
doing
so
so
the
next
step
is
getting
that
into
a
partition
and
then,
finally,
when
you
put
this
whole
thing
together,
early
plug
that
usb
into
into
the
raspberry
pi
and
you
boot
up,
you
can
see
a
flat
car
booting.
D
D
So
I
would
recommend
to
read
that
blog
post,
the
link
is
there,
but
if
you
can
also
use
the
search
engine
to
search,
maybe
flat
current
raspberry
pi
and
it
should
pop
up
and
then
the
next
outlook
is
like
getting
the
like
om
image
published
as
dilu
mentioned.
This
is
right
now
a
bit
hacky,
so
it
would
be
getting.
It
would
be
better
to
get
like.
D
And
then
trying
it
on
probably
during
five.
So
these
are
the
futures
things
that
we
could
look
forward
to,
and
I
should
say,
like
the
reason
for
me,
is
primarily
building
this
home
lab
was
taken
around
and-
and
this
provides
a
very
good
infrastructure
as
at
least
with
r54.
It
comes
very
close
and
you
could
really
run
clusters
and
stuff
production
level
stuff
on
these
on
your
home
lab.
E
E
So
first
I'm
going
to
give
a
small
brief
about
what
locksmith
is
locksmith
is
the
reboot
manager
for
the
flat
crane
instance.
It
runs
as
a
daemon
in
the
flat,
for
instance,
and
it
relies
on
its
city
to
reboot
the
setup
cluster
of
mission.
It's
accuracy
semaphore
and
do
the
reboot
stuff,
and
the
next
thing
is
what
is
fleet
lock?
Fleet
lock
is
a
required
response.
E
Protocol
means
the
client
can
request
some
functions
and
it
is
gonna
response
back
if
it
is
valid
or
not
so
it
can
do
in
in
the
basic.
It
can
do
mainly
two
things.
One
is
recursive
lock
and
unlock
effect.
First,
one
is
to
accurate.
The
lock
is
a
recursive
lock,
and
the
unlock
key
field
is
the
unlock
the
lock
if
it
has
acquired
some
locks.
E
So
these
locks
are
on
means.
The
client
created
the
lock
can
only
release
it
next
slide,
yeah,
so
why
we
should
switch
to
fleet
lock.
For
first
thing
is
the
flexibility
we
want
to
give
users
flexibility
to
use
whatever
they
want
as
long
it
supports
the
fleet
of
fleet
lock
protocol
and
we
had
in
previously
we
had
a
concrete
implementation
of
the
hcd.
So
we
want
to
remove
that
cd
part
and
third
thing
is
to
ensure
compatibility.
E
Air
lock
is
the
default
fleet
lock,
client
that
we
are,
that
is
provided
in
the
fedora
core
way.
So
we
want
the
flat
cut,
is
the
kind
of
os
from
coreos?
So
we
want
to
give
compatibility
with
that.
Fourth
thing:
is
we
even
could
offer
public
lock
surveillance
if
someone
wants
to
use
their
public
lock
server
with
any
application
that
runs
their
suppose
fleet
lock
protocol,
they
can
use
it.
E
You
can
track
our
issue
in
the
link
next
slide,
so
things
I
learned
from
from
doing
this
work
is
understanding
the
fleet
lock
protocol,
how
it
works,
and
it
is
a
http
based
line.
So
I
learned
a
lot
about
http
and
client
server
protocols
and
third
thing
I
learned
is
how
locks
and
unlocks
happen
and
behind
the
scene,
how
fleet,
lock
is
doing
things
and
what
I
did
actually
a
lot
of
refactoring,
because
we
had
a
lot
of
concrete
implementation
of
hcd
and
semaphore
in
the
locksmith.
E
E
So
this
is
what
is
the?
What
is
our
current
behavior?
E
So
nebraska
is
the
update
server
and
whenever
there
is
a
new
release,
so
it's
gonna
inform
to
update
engine
of
the
os
and
the
updating
is
gonna,
tell
locksmith
the
demand
or
that
we
need
to
remove
sorry
sorry,
we
need
to
reboot
a
set
of
cluster,
so
it's
gonna
manage
this
mr4
and
it's
gonna
use
hcd
to
accurate
the
lock
and
all
these
things
and
it's
gonna
reboot
its
the
set
of
clusters.
E
I'll
show
a
current
behavior.
So
next
slide-
and
this
is
where
going
I'm
going
to
do
like
the
same
thing.
Whenever
there
is
a
new
release,
it's
gonna
tell
the
update
engine
and
updates
and
engine.
C
E
Gonna
tell
the
locksmith
that
we
have
to
reboot,
then
locksmith
day
is
gonna.
Tell
the
it
is.
E
It's
gonna
tell
to
the
the
heat
lock
client
that
that
we
want
to
reboot
a
set
of
clusters,
so
it
is
like
the
situation
where
people
is
using
any
client
that
supports
fleet
lock
protocol,
so
the
fleet
lock
protocol
client
is
going
to
manage
all
that
city
and
software,
and
it's
gonna
response
back
to
the
locksmith
that
I
I
have
so
this
camera
for
locks
and
and
now
you
can
reboot
so
in
the
next
slide-
and
here
we
are
here-
it
is
our
the
default
behavior.
E
What
is
going
to
ship
with
the
locks
locksmith?
So
in
the
same,
the
nebraska
is
going
to
tell
the
update
engine
and
update
is
going
to
tell
the
locksmith
and
locksmith
they
will
tell
to
airlock
lock
is
a
default
fleet
lock
plant
is
that
is
going
to
be
shipping
with
the
os
and
air
lock
is
going
to
manage
all
the
things
and
air
lock
is
going
to
response
back
to
locksmith
that
yeah.
I
have
activated
the
lock
and
you
can
reboot
this
set
of
clusters.
E
B
So
demo
time
thanks
anybody
once
again
for
your
work,
yeah
and
it's
yeah.
Well,
it's
like
it's
all
right!
Everything
was
perfect.
So
let's
play
the
demo,
please
it's
a
simple
demo
of
using
hcd
and
air
lock
into
a
flat
core
instance.
So
let's
first
have
a
look
to
the
container
linux
configuration
we
basically
spin
up
airlock
server
and
also
it's
the
node
instance.
Then
we
ssh
into
a
flat
car
instance
and
this
instance
is
supposed
to
reboot
because
it's
quite
outdated.
B
B
B
And
after
a
couple
of
seconds
we
should
see
a
signal
of
reboot
is
needed,
so
basically,
locksmith
asked
to
lock
airlock
ask
to
hcd
for
rebooting
and
yeah.
That's
it
our
instance
is
going
to
reboot
as
usual.
So
this
is
basically
the
default
behavior.
We
want
to
ensure
when
field
talk
will
be
merged
to
locksmiths
like
so,
we
will
ensure
compatibility
with
previous
behavior
and
yeah.
B
It
will
mitigate
the
update,
but,
as
daniel
would
have
said,
the
main
goal
of
flick,
like
integration
is
basically
to
provide
flexibility
to
the
user
and
like
so,
you
can
use
whatever
they
want.
As
long
as
it
clicks
on
players
behind
and
as
I
mentioned
into
the
chat,
there
is
even
some
community
contribution
using
api
gateway
from
aws
plus
dynamodb
in
order
to
yeah
to
use
the
this
system
of
this
block
protocol.
C
All
the
huge
thanks
from
my
end
anyway,
that's
exciting
word.
C
Do
we
want
to
look
at
this
clc,
or
are
we
good
to
go?
No,
that's
all
right!
We're
good
to
go!
Gotcha
you'll
find
all
those
links,
of
course,
in
the
slides
after
we
publish
them,
usually
a
few
days
after
this
meeting,
all
right
now
heading
off
to
cyan
for
the
release
planning
so
yeah.
Do
you
want
to
share
your
screen
or
do
you
want
me
to
share
the
screen.
D
Right
so
I
have
created
so
just
starting
with
that.
We
are
in
progress
of
releasing
an
alpha
release,
which
is
three
one
one
five
we
had
had
some
blockers
there
very
minor
blockers,
but
they
are
out
of
the
way
and
we
should
be
like
things
are
looking
good
should
we
might
do
the
release
tomorrow,
but
let's
see,
but
things
are
looking
good
as
of
now
so
so
right
now
we
are
just
doing
the
alpha
release.
D
Okay,
I
forgot
to
mention
okay
on
24th,
we
are
planning
the
next
release,
which
is
I'll.
D
Add
that,
to
the
add
the
note
there,
so
we
will
be
having
alpha
beta
and
stable,
so
beta
and
stable
will
be
major,
like
I
suppose,
and
alpha
will
again
be
a
major
one
and
the
reason
being
we
have
beta
is
stable
around
for
some
time
now,
but
anyway,
so
moving
ahead.
So
right
now
like
we,
I
have
created
the
column.
D
So
folks,
if
you
are
working
on
any
issues,
then
feel
free
to
add
them
to
reports
and
then
so
there
are
two
boards,
the
24th
of
january,
one
and
the
seventh
february
one,
and
there
are
a
few
planned
packages
upgrades
that
I
have
mentioned
in
there,
we'll
be
going
through
those
in
the
next
two
weeks
and
or
one
thing
or
beginning
of
the
year.
We
had
two
system
day,
250
release
so
giving
it
some
time
and
targeting
it
with
the
7th
of
february
release.
D
So
that's
mostly
it,
but
given
we
are
starting
off
with
the
year
and
so
expect
a
few
updates
to
the
boards
as
we
go
along
over
the
next
two
weeks.
So
yeah,
that's
mostly
from
my
side
but
folks
as
if
you
do.
You
have
any
issues
that
you're
working
on
or
something
that
I
missed.
That
needs
to
be
tackled.
D
If
I
just
see
the
chat-
okay,
if
not
I'll,
encourage
like
if
you're
working
on
asia
blue
file
issue
for
it
and
add
the
columns
are
not
created,
so
you
can
just
add
the
color.
Add
the
columns
in
there
like,
if
you're
working
on
them
to
add
the
in
progress
or
they're,
ready
to
release
columns
yeah.
That's
that's
it
for
this
release,
but
yeah
folks
or
tuning
in
later
do
remember.
We'll
update
this
board
as
we
go
along.
C
Thank
you
very
much
sayon.
So,
as
science
said,
if
you
have
an
issue
to
scratch,
there
are
almost
two
more
weeks
for
you
to
file
a
pr
and
get
it
merged.
If
you
want
to
be
part
of
the
next
round
of
releases,
that
will
be
all
channels,
steady,
patch
releases
for
beta
unstable
and
there
will
be
a
new
offer
version
that
may
include
your
favorite
feature.
C
Back
to
the
slides
and
we've
arrived
at
the
end
of
the
meeting,
so
if
you'd
like
to
participate,
if
you
like,
playing
with
operating
systems,
if
you
use
flat
car-
and
there
is
this
one
feature
that
you've
always
missed,
then
jump
aboard
reach
out
reach
out
to
us
and
work
with
us
everybody's
welcome
in
the
project.
C
Calling
once
calling
twice
all
right,
thank
you.
Everybody
for
joining
you'll
find
us
on
that
slide
kind
of
got
way
too
far.
Behind
you
find
us
on
metrics,
you
find
us
on
github.
You
can
interact
with
us
in
a
number
of
ways
and
we're
on
twitter
as
well
so
see
you
around,
have
fun
with
flatcar
and
see
you
on
the
release
planning
at
the
end
of
general.