►
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).
A
A
Okay,
folks,
you
should
be
seeing
my
screen
before
that
you
should
have
seen
resizing
the
window.
Air
share.
My
screen.
Welcome
to
the
october
flight
community
call.
We
are
one
week
late,
because
we
skipped
last
week
there
was
kubecon
going
on
and
everybody
was
just
busy
with
kubecon.
A
So
you
have
a
number
of
items
today
for
you
and
we
need
to
skip
over
one
regular
section
that
we
have
but
more
on
that,
after
the
welcome
as
usual,
we
just
go
around.
Everybody
introduces
themselves
in
a
few
seconds:
hi,
I'm
kilo,
I'm
I
work
for
microsoft.
I'm
the
manager
of
the
team
that
maintains
flat
car
there
as
well
and
the
car
strives
to
be
a
very
active
and
awesome
community
product
community
project.
E
F
Hi
so
hi
everyone,
I'm
syan
joining
from
india.
I
also
work
with
the
flat
card
team
in
microsoft.
I
primarily
look
around
for
the
releases
and
currently
working
on
the
automation
pipeline
going
next
donsoo.
G
H
New
headphones
does
it
work
now
yeah?
Okay,
I
was
double
mute,
sorry
about
that
hi
danielle,
currently
in
barcelona,
usually
in
berlin,
also
at
a
flat
car
team
for
microsoft,
the
program
manager
for
them
64
effort
who
was
not
talking.
A
Cool
thanks
everybody.
So
let's
look
at
the
news
and
happenings
around
flat
calinox.
In
the
last
month
we
had
a
little
bit
of
a
scramble
in
the
last
two
weeks,
because
we
had
an
quite
urgent
unscheduled
amount
of
work
to
do
in
the
build
infrastructure.
A
We
detected
the
overuse
of
a
google
bucket
which
we're
using
both
for
continuous
integration
and
for
public
builds.
So
you
folks
have
been
using
those
as
your
binary
caches
and
sources
for
the
sdk
hubble,
which
was
perfectly
fine,
but
that
overuse
which
we
expect,
which
we,
which
we
think
wasn't
a
malicious
thing,
just
people
building
flat
car
kind
of
stretched,
our
our
google
bucket
a
little.
So
we
were
required
to
put
that
private
and
that
impacted
both
the
ci
and
releases
as
well
as
the
public
builds
that
you
folks
out.
A
There
have
been
doing
we
scrambled
and
worked
hard
to
mitigate
those
issues,
and
the
current
status
is
that
we
introduced
two
new
services
that
public-facing
services.
First,
there's
a
binary
package
mirror
for
release
binaries.
We
expect
this
to
be
the
main
thing
that
people
building
flat
car
would
be
using
from
here
on,
and
we
also
have
a
public
facing
build
cache
that
caches
ci
items.
This
is
mainly
interesting
if
you
are
doing
flat
cover
that
works
directly
on
the
main
branches,
so
the
next
alpha
release
so
to
say,
and
those
are
also
publicly
cached
now.
A
The
next
steps
is
that
we
are
going
to
release
a
update
to
all
of
the
flat
card
channels,
double
included,
a
lot
of
goodies
planned
in
the
previous
release,
planning
meeting
actually
and
also
a
new
mental
update,
and
that
will
wrap
up
all
of
those
changes
that
you've
seen
and
the
new
services
and
will
just
work
automatically,
just
as
you
use
just
as
you're
used
to
and
also
we
will
not
have
a
release
planning
in
this
call,
because
we
were
basically
busy
getting
our
infrastructure
back
to
work
and
introducing
those
new
services
to
mitigate
the
impact.
A
Something
that
has
pushed
out
the
releases
for
for
the
last
two
weeks
they're
now
coming.
We
expect
them
to
be
published
later
this
week
and
on
the
more
exciting
side
there
is
hector
fest
going
on
and
flat
car
linux
is
participating.
So
if
you
have
a
pr
open
in
any
of
our
repos
check
out
this
tag
to
for
the
pr
to
be
counted
against
hacktoberfest,
so
you're
part
of
the
of
the
party,
and
should
you
be
planning
to
file
a
commit
to
a
project
that
doesn't
have
the
tag?
A
Just
let
us
know
in
the
metrics
chat
and
we
can
discuss
adding
the
stack
to
further
repos
we've
now,
we've
for
the
time
being,
target
the
repos
that
are
most
common
and
I
get
most
patches,
but
if
you're
interested
to
work
on
something
else
flat.
Car
related
we're
actually
happy
to
add
this
tag.
Accordingly,.
A
All
right,
let's
get
to
the
death
department,
we
have
a
few
development
projects
going
on
and
we'd
like
to
introduce
three
of
those
today.
Just
to
give
you
an
idea
of
what
keeps
us
busy
apart
from
well
overcoming
our
ci
issues
and,
let's
start
with
the
ignition
v3
support.
But
here.
E
E
Provisioning
ignition
is
just
going
to
run
once
in
the
init
ram
fs
stage,
so
it
basically
use
design
configuration
and
the
goal
of
ignition
is
to
create
some
files
to
set
the
host
name
like
in
the
example
to
provide
some
drop-in
for
systemd
or
providing
ssh
key
to
the
instance
like
we
can
see
on
the
on
the
screenshot.
The
version
of
ignition
currently
supported
with
flat
car
is
only
the
version
2
and
the
goal
of
ignition
v3
support
is
to
actually
provide
support
for
version
3
and
version
2.
E
next
slide,
please,
so
why
we
want
to
support
both
versions.
It's
actually
to
to
limit
the
braking
change.
We
want
to
introduce
into
flat
car.
So
basically
we
want
users
to
be
focused
on
the
workloads
they
run
and
not
to
be
not
to
follow
each
breaking
change
of
flat
car.
So
that's
why
we
want
to
bring
support
for
v2
and
v3,
and
this
is
quite
something
because
v2
and
v3
are
not
compatible
from
a
code
based
point
of
view,
but
also
from
a
configuration
pull
up
next.
E
Okay,
thank
you.
So
this
is
currently
how
it
works
in
the
implementation
we
we
did
to
support
both
version.
We
basically
take
an
input,
and
this
is
the
ignition
file
we
just
check
if
it's
version
3
or
not,
if
it's
a
version,
3,
let's
continue
as
usual,
and
if
it's
a
version
2.
Let's
just
translate
this
ignition
using
ignition
converter
lib,
which
is
provided
by
core
os.
E
So
once
we
did
the
translation
to
e3,
we
can
just
continue
as
regular
to
boot
the
instance
and
at
each
step,
if
we
have
an
error,
we
just
land
into
the
emergency
target
of
systemd.
So
this
is
basically
a
simple
mechanism
and
yeah
it
works
for
for
now.
So
next
slide,
please!
E
So
what
is
this
current
status
there
is
appear
opened
on
the
flat
card
linux
ignition
repository
to
submit
this
logic
of
a
translation.
We
also
have
appeared
on
the
chorus
of
early
in
order
to
bring
this
new
ignition
into
flat
car,
so
it's
currently
being
tested-
and
there
is
a
two
pier
in
the
upstream
to
support
more
edge
cases
of
ignition
converter.
E
And
yes,
here
is
okay,
except
for
some
ignition
version,
one
test
which
is
going
to
be
dropped
in
the
next
release
of
flat
car,
but
yeah.
We
will
keep
in
touch
regarding
this
and
yeah.
If
you
want
to
play
with
it
to
test
it
just
run
the
sdk.
Now
we
can
run
the
sdk,
so
we
need
to
test
it
to
try
it,
and
here
we
build,
we
need
frame
fs
using
the
ignition
built
locally,
so
yeah,
that's
it
for
ignition.
E
E
From
from
cyan,
I
guess
from
the
next
slide.
A
A
All
right,
everybody's
happy
all
right.
So
following
matthew
cyan,
can
you
give
us
a
quick
intro
to
the
vlog
project.
F
Sure,
thanks
thanks
hello,
so
in
the
release
pipeline
we
are
introducing
a
new
project
called
vlog.
It's
still
in
a
very
bare-boned
state
and
primarily
can
be
termed
as
poc.
So
this
is.
This
project
came
out
of
idea
that
when
we
are
doing
a
release,
we
usually,
if
you
have
seen
the
release,
notes,
we
link
the
projects
and
the
version
number
and
during
the
process
of
building
the
series
note,
it
takes
a
good
amount
of
time
to.
F
Build
that
whole
release
notes
and
the
change
lock
linking
to
the
changelog
part.
So
what
we
are
trying
to
do
here
is
we
are
introducing
this
automated
way
to
fetch
all
the
change
logs,
and
this
would
also
have
a
community
presence.
So
if
you
have
a
projects,
this
could
be
a
standardized
way
to
update
your
basically
a
single
source
where
you
can
have
your
change
log
and
you
can
monitor
the
change
log,
so
it
would
as
a
maintainer.
F
It
would
help
us
to
track,
see
the
changes
and
also
like
we
could
just
publish
the
change
logs
through
vlog
and
for
general
public.
This
could
be
not
even
associated
with
flat
car
or
associated
with
the
flat
card.
They
can
just
see
how
the
projects
are,
and
they
can
just
click
on
the
links
and
see
the
changelog.
So
so,
if
you
see
the
there
are
something
you
see
a
supported
connector,
so
we
will
be
supporting
github,
lwn
and
various
others
in
the
in
the
future.
F
So
the
idea
is
to
pull
change
logs
for
various
different
places
and
source
it
into
one
place
and
the
changer
aggregator
would
show
as
a
list
menu
and
if
you
click
those
items
like
right
now,
on
the
right
hand,
side
you
see
mantle
so
on.
So
that's!
Basically,
when
you
click
on
the
version
number.
F
You
see
the
mantle
change
change
log
of
that
particular
release,
and
that
is
right
now,
because
mantle
is
on
github
and
we
do
the
use
github
releases,
so
that
is
getting
pulled
from
github
directory.
So
the
plan
is
to
add
more
connectors
and
if
you'd
like
to
contribute,
do
pingas
on
matrix
channel
and,
as
I
told
like,
this
is
a
poc
and
we
will
be
heavily
working
on
this
so
feel
free
to
connect
with
us
to
help
on
this
project.
F
Yeah,
that's
from
my
side,
back
to
utila.
A
The
third
and
final
mini
project
that
we'd
like
to
present
is
actually
something
I
have
been
doubling
with
lately
and
that
is
the
current
sdk
is
using
cork
to
instantiate
itself
and
to
put
you
into
a
change
room
which
then
has
a
number
of
point
mounts
mounted
into
the
change
route
in
order
to
work,
and
that
is
basically
the
container
concept
re-implemented
in
cork.
So
I
thought
hey.
Why
not?
You
know:
go
the
full,
the
full
distance
and
use
containers
right
away
and
turns
out
actually
after
a
quick,
deep
dive.
A
It's
not
that
hard.
So
I
came
up
with
a
prototype.
That's
currently
work
in
progress,
there's
a
number
of
concepts
in
my
prototype
that
still
need
to
be
aligned
it.
It
basically
aims
to
be
a
technology
demo
for
the
time
being
after
we
clarified
until
we
clarified
all
of
the
open
items
all
right.
So
it
should
of
course
enable
you
to
make
flat
commodifications
a
lot
easier.
Then
you
can
do
that
now.
A
It
emulates
the
existing
sdk,
which
doesn't
really
matter
for
for
new
developers,
but
for
developers
used
to
the
flat
car
sdk
they'll
find
themselves
in
a
known
environment.
It
eases
ci
integration
and
where
we've
started
to
actually
use
this
for
for
ci
builds,
makes
handling
a
little
easier.
There
is
a
work
on
progress
branch
and
pr,
as
I
said,
it's
more
like
a
proof
of
concept
by
now,
and
I
have
a
very
small
demo
so
right
here,
I'm
in
the
sdk
root.
A
So
it's
flat
conscript
and
I'm
on
my
work
on
purpose
branch
and
this
uses
the
the
versioning
that
klepka
used
as
well.
So
if
we
look
into
a
file
that
will
end
up
in
the
container.
A
This
is
basically
based
on
a
cloud
cover
version.
It
uses
an
sdk
that
happens
to
be
available
on
the
github
container
registry,
which
we've
been
playing
around
with
as
well.
What
you
do
now
is
you
just
start
a
script,
and
it
doesn't
really
matter
whether
you
have
the
sdk
locally
or
not,
and
it'll
use
the
sdk
version
from
the
version
kxt
and
just
put
you
into
the
sdk
container,
which
you
can't
see,
because
the.
A
This
green
part
didn't
show
okay,
so
you're
in
the
container
you're
still
in
the
scripts
repository
which
is
bind
mounted
into
the
container
and
volume
mounted
into
the
container,
and
anything
else
around
here
is
containerized.
A
A
And
files
there
and
you
can
exit
the
container
and
one
of
the
interesting
ideas
here
is
that
as
long
as
this
container
exists,
it
has
a
it
has
a
it
has
a
calculable
name
so
to
say
as
long
as
containers
there,
it
will
be
reused,
so
that
file
is
still
there
and
if,
for
some
reason
you
don't
need
your
containerized
work
anymore.
A
All
right
that
was
our
demo
section
and
development
project
section.
Let's
get
to
the
arm.
64
status,
update
william,
and
this.
D
Menu-
yes,
indeed,
all
right
so
short
update
on
the
arm
front,
but
great
news.
Let
me
get
that
first
slide,
tilo
all
right!
So,
just
earlier
today,
we've
finally
landed
the
pull
kit
0.119
update,
which
resolves
the
last
test.
Failure
in
our
arm
64
suite
this
means
that,
as
part
of
our
standard
release,
cadence
and
barring
any
unforeseen,
breakage
or
roadblocks
arm64
will
be
promoted
to
beta
either
later
this
month
or
in
early
november,
and
will
thereafter
be
promoted
to
stable
in
december
abouts.
A
A
And
that
already
brings
us
to
the
end
of
the
base,
call
if
you're
interested
in
contributing,
if
you
wanna
scratch
your
own
edge
with
container
operating
systems,
we're
here
and
we're
ready
for
your
contributions.
So
please
reach
out
join
the
community,
become
a
contributor
and
or
just
drop
by
and
chat
to
us.
E
A
It's
pretty
big
so
like
the
full
sdk
with
support
for
building
both
arm
and
x86
operating
system.
Images
is
that
about,
I
think,
3.5
gigabytes.
A
A
All
right:
well,
then,
thanks
everybody
for
participating,
see
you
next
week
in
the
release
planning
or
in
the
community
call
november.