►
Description
Distribution team demo on setting up a Gitlab Distribution review environment using virtual machines on an M1 mac.
A
Of
course,
hello
and
welcome
to
the
distribution
team
demo
I
am
Robert,
and
today
we
are
going
to
be
looking
at
the
rundown
of
the
challenges,
as
I
am
trying
to
solve
the
problem
of
virtualization
on
the
maccam1
and
when
I
say
virtualization,
I
kind
of
need,
virtualization
scale,
which
is
to
say
to
replicate
the
way
that
I
do
my
workflow.
A
So
the
basic
challenges
are
a
couple
for
one
for
those
to
please.
David
Baker
currently
does
not
have
support
on
the
M1
for
virtualbox,
the
other.
The
open
source
solution
that
most
Mac
users
have
used
in
the
past.
A
Virtualbox
currently
has
a
beta
out,
but
the
combination
of
it
and
then
a
mysterious
issue
in
Mac
OS
is
causing
problems
and
we'll
get
into
what
that
specific
issue
is
here
in
a
little
bit.
But
let's
just
start
with
a
screen,
share,
go
ahead
and
share
my
experience.
A
Desktop
two
and
sure
okay,
so
we
are
in
my
test
environment
and
one
of
the
things
to
know
about
the
the
M1
is
most
of
us
use
Homebrew.
A
A
A
So
podman
the
way
it
works
is
it
creates
a
virtual
machine
in
Apple's
hypervisor
framework.
Now
what
Apple
has
done
with
research?
Mac
OS
is
created
an
actual
framework
for
hypervisors,
so
podman
leverages
that
and
for
those
who
don't
know,
Dr
desktop
did
the
same
thing.
It
would
create
a
in
the
background
would
be
a
beehive
virtual
machine
and
loads
containers
to
it.
Podman
does
something
similar,
but
using
the
new
hypervisor
framework.
A
So
when
you're
using
containers
on
a
Mac,
you're,
technically
creating
a
virtual
machine
spawning
containers
inside
of
it
so
with
this
and
the
fact
that
this
is
downloadable
either
through
Brew
or
you
can
download
it
Direct.
But
this
basically
demonstrates
that,
yes,
we
can
run
qw
machines,
so
we
know
the
technology
worked,
but
there
are
some
interesting
side
effects
for
one.
You
have
to
change
your
virtual
virtualization.
Actually,
now
Homebrew
does
allow
you
to
have
qmu,
but
the
defaults
still
kind
of
Falls
to
x86.
A
Now
you
can
get
away
with
that,
because
if
you
have
installed
the
Rosetta
underlying
framework,
it
will
kind
of
fake
you
out,
you'll
think
it's
working,
but
you're
actually
running
x86
code
on
top
of
the
arm
framework
and
what
we
want
to
get
to
is
actually
using
arm
64
or
ar-64
architecture
default
virtual
machines.
Now
there
are
a
couple
of
things
about
running
ar-64
virtual
machines,
one
they
because
the
nature
of
how
Mac
OS
has
implemented
EFI,
which
is
extensively
accessible,
firmware
interface,
which
is
the
firmware
that
is
underneath.
A
Like
the
pre-boot
right,
you
get,
you
get
power
on,
you
get
the
firmware
or
the
BIOS,
and
then
that
bios
will
hand
over
to
the
kernel,
which
is
the
hand
to
it,
to
user
space
four
ar-64
on
Mac.
You
must
use
EFI
if
you've
ever
used,
qmu,
liver
and
all
that
you've
probably
seen
C
bios
or
some
words
about
pop-up.
A
So
let's
take
a
look
first
at
the
technology
behind
this,
for
those
who
haven't
used
it
before
there's
this
handy
thing
called
first
is
a
virtual
machine
interface
if
you've
used
qmu
in
verse
before
it's
basically
the
same
thing,
but
it
allows
you
to
Define
your
virtual
machine
as
what
they
call
a
domain
in
XML.
A
A
And
the
thing
to
notice
here
you
see
your
EFI
firmware
now
when
I
test
I
want
to
use
default
setups,
so
I
don't
want
to
install
every
time.
So
what
you
see
here
this
is
this
works,
and
this
is
kind
of
my
first
iteration
was:
can
I
get
it
to
boot
up
and
can
I
get
it
to
allow
me
to
to
install
and
this
kind
of
works,
but
I
want
to
get
Packer
to
install
as
well,
because
we
do
have
defaults.
A
A
And
this
is
a
personal
library
that
I
have
that
I've
created
for
myself
for
other
things.
I
adapted
for
here
is
that
you
have
to
change
things
so
in
Packard
that
EFI
thing
we
talked
about
Homebrew
puts
this
code
into
into
a
you
have
to
override
this,
because
the
fault
for
this
is
user,
local,
qmu
and
then
a
bios.
So
we
have
to
overwrite
it.
A
You
also
have
to
set
have
to
set
the
default
virus
file
reference.
What
is
a
vars
file
in
extensible
firmware
interface,
when
you
load
like
when
your
computer
boots
up
with
EFI,
unlike
bios,
which
loads
all
your
options
in
your
configuration
into
a
a
small
sub
file?
That's
loaded
on
the
heart
on
the
disk
EFI
is
like
a
separate
partition
where
your
variables
are
stored,
fun
fact
on
some
systems,
if
you
get
too
many
EFI
variables,
your
machine
will
refuse
to
boot
will
fail.
A
A
A
It's
in
the
qmu
arcs,
because
qmu
there's
some
problems
for
one.
You
have
to
set
up
your
your
P
Flash.
This
is
part
of
how
it
knows
how
to
store
the
variables
as
you
set
up
the
machine.
A
Now
you
see
this
dunk
bars.
This
is
a
it
takes.
The
default
bars
copies
it
in
and
then
creates
a
new
one
based
on
the
settings.
You're
creating
I
have
to
make
turn
this
to
a
variable.
But
again,
that's
my
iso
download
for
the
installer
again
with
Packer
we're
going
to
create
an
image,
but
this
all
of
this
setting
up
the
ports
the
devices
all
of
this
is
because
to
Mu
right
now
doesn't
easily
detect
a
lot
of
the
devices
in
the
hbf
setup,
and
that
is
something
that
you'll
see
up
here.
A
We
commented
it
out
put
your
accelerator
on
a
Mac
has
to
be
hbf
and
we
set
that
up
down
here
and
options.
One
of
the
big
challenges
we
face
is
that,
depending
on
where
you
set
certain
options,
it
may
set
twice
so
you
have
to
pick
and
choose
like
here.
The
machine
type
is
convert
8.0
and
that
gives
us
the
correct
machine
type
emulation
to
get
these
devices
again.
A
There's
a
lot
of
weird
things
here,
and
this
is
because
pmu
and
Homebrew
a
lot
of
the
defaults
just
assume
x86
and
86
x86
Hardware,
so
we're
so
for
right.
Now
we're
basically
climbing
the
hill,
both
climbing
the
hill,
going
going
both
ways
because
it
works.
But
you
have
to
override
everything
to
get
into
this
ar-64
mindset,
which
is
to
say
that
you
go
from
bios
to
EFI.
A
You
have
a
framework,
you
have
the
device,
the
way
device
trees
presented
as
different,
so
you're
dealing
with
a
lot
of
problems,
so
this
qualm
memory
believe
it
or
not,
is
in
mandatory
field
for
Packer.
You
have
to
set
that
up
now.
I've
not
had
this
at
this
for
just
running
the
machine,
but
for
Packer,
for
whatever
reason
it
it
freaks
out.
If
I
don't
set
this
right
and
give
it
this
mock
virtual
RAM
memory
system
so
and
all
this
was
just
trial
and
error.
A
A
A
C
A
Was
the
product
of
of
quite
a
bit
of
work.
C
C
C
A
Let's
see
other
things
note
yes,
so
now
one
of
the
things
that
is
not
working
in
vagrant
is
that
when
you,
when
you
start
up
the
machine,
you'll
see
vagrant
up
it'll
finish.
A
But
if
you
check
the
error
code,
the
answer
to
error
code
256-
and
this
comes
back
to
when
we
talk
about
what
are
the
challenges.
So
one
of
the
things
that
I
do
is
I,
stand
up,
multiple
virtual
machines
at
a
time,
so
I
want
orchestration
method
for
standing
up,
say
three
radishes
or
standing
up
three
database
instances
or
stand
up
like
just
a
partial
of
an
aha
environment.
So
I
can
do
testing
that
doesn't
work
right
now,
because
I
can't
orchestrate
it,
and
there
is
a
reason
for
that.
A
Typing
checks
for
the
morning:
I
guess
all
right,
you
can
check
attributes
now
this
right
here.
This
is
the
current
blocker
that
I've
hit.
Now
this
is
a
tag
that
Apple
puts
on
machines
on
on
various
files
on
your
machine.
What
this
means
is
that
this
device
is
not
allowed
to
make
certain
changes
unless
it's
code
signed.
A
A
Thank
you
so
I
have
this
bridge
set
up
on
my
machine
right
because
virtual
machines
there's
a
couple
things
you
need
to
do.
You
can
have
the
virtual
machine,
it
connects
the
internet,
but
also
you
can
have
it
talk
to
other
machines.
Only
it's
called
an
isolated
virtual
Network
or
you
can
Bridge
it
and
bridging
it
does
this
thing
that
allows
the
the
host
and
other
machines
to
talk
to
each
other
with
names
on
my
setup.
Will
this
be
a
public
to
the
world
video
or
is
it
just
public
to
us.
A
Okay,
I,
don't
really
want
to
expose
my
internal
lab
configuration,
but
all
my
machines
have
have
DNS
set
up
so
that
when
they
come
up,
I
can
route
packets
between
all
the
machines.
A
With
that
said,
I
can't
get
this
to
work
because
I'm
trying
to
use
the
the
tap
driver,
the
tap
Network
driver
to
connect
to
basically
tap
in
a
interface
on
the
bridge
that
doesn't
work
because
Mac
OS
says
unless
you're
Co
assigned
code
package.
You
cannot
do
that,
and
that
was
the
latest
thing
that
I
hit
I
hit
that
last
night
knocking
my
head
on
the
wall
for
a
while,
but
that
is
kind
of
the
window.
A
So
current
state
I
can
stand
up
a
virtual
machine
and
it
can
run,
but
it
cannot
create
a
network
on
the
bridge.
It
can
only
create
a
netted
with
pass-through,
no
ver,
no
nodded
with
pass-through
machine.
A
So
if
I
want
to
run
say
three
instances,
I'd
have
to
give
each
a
different
forward
and
Port
of
my
machine.
That's
the
current
state
of
things.
Now
there
is.
There
are
two
ways
around
this:
one
is
somebody
from
here:
signs
up
for
a
apple
developer
license
and
we
signed
the
package
and
we
actually
create
this
I.
A
Don't
know
if
that's
tenable
I
certainly
don't
want
to
maintain
that
much
stuff
I'm
going
to
talk
to
some
friends
at
qmu
upstream
and
libert
upstream
and
see
if
there's
any
appetite
for
that,
because
we
have
a
Apple
developer
license
for
signing
the
Fedora
media
writer
package.
If
any
of
you
have
installed
Fedora,
you
know
you
can
download
the
Fedora
media
writer
and
write
that
package
on
Mac
OS
and
it's
a
signed
application.
A
A
Utm
now
UTM
is
open
source,
but
they
have
to
go
through
Apple
for
the
code
signing
thing,
but
this
creates
virtual
machines.
Now
the
problem
with
UTM
is
that
while
it
does
do
this
and
it
does
claim
to
be
qmu
without
the
headache
what
it
doesn't
do,
is
it
doesn't
give
you
a
a
programmatic
interface
like
I,
just
want
to
set
up
and
automate
installs
now
they've
been
adding
some,
but
this
is
kind
of
the
next.
The
next
thing
to
work
on.
A
They
provide
an
apple
script
interface,
not
a
ruby
interface,
not
a
programmer's
interface
but
an
apple
script
interface,
and
so
there's
a
lot
of
discussion
and
just
to
kind
of
bring
in
some
of
the
research
right.
So
here's
the
discussion
Upstream
about
VM,
Network
and
again.
This
is
because
you
need
an
elevator
permission
which
this
cosine
won't
allow,
but
you
run
into
this
because
of
the
lack
of
code
suck.
A
A
So
the
other
thing
that
we
can
do
with
this
would
be
to
use
something
called
Ruby,
osas
or
ASAS,
and
create
a
vagrant
driver
for
UTF,
which
I
think
is
the
next
thing
I'm
going
to
try
and
work
on
in
my
spare
time,
because
the
only
way
to
get
back
to
this
workflow
locally
is
going
to
be
to
get
UTM,
which
has
the
code
signing
set
up
to
accept
bigger
inputs.
And
it
didn't
accept
that
six
months
ago,
four
months
ago,
they
just
recently
and
I'm.
Looking
for
the.
A
Somebody
wrote
a
thing:
it
doesn't
quite
work
so
well,
but
there's
been
a
lot
of
discussion
around
how
to
make
this
work,
both
an
upstream
limbert,
Upstream,
vagrant
and
right
now.
I
think
the
general
idea
is
because
of
the
code
signing
is
to
try
and
add
a
vagrant
plug-in
for
utms,
and
so
that's
kind
of
the
state
of
the
world
right
it
worked.
A
You
have
to
do
a
lot
of
twiddling
to
tell
it
which
firmware
to
use
because
EFI
not
bios,
you
have
to
kind
of
add
a
lot
of
different
device
drivers
because
it's
not
Auto
detecting
them.
Yet
there
is
some
work
going
on
Upstream,
but
a
lot
of
the
support
came
in
with
qmu7
we're
at
7.0.8
right
now,
so
we're
getting
patches
as
things
come
in
some
of
the
challenges,
the
core
functionality
of
how?
A
Let's
turn
off
my
screenshot
right
now
of
how
all
this
works
is
that
you
use
a
a
ton,
tap
networking
driver
to
create
a
tap
interface,
to
add
it
to
your
bridge,
to
allow
connections
to
allow
DNS.
All
of
that
is
blocked
by
Mac
OS.
So
that's
kind
of
that's
kind
of
the
the
big
the
big
boulder
in
our
way
UTM
code
size.
A
So
it
gets
around
that
but
UTM
uses
Apple
scripts,
which
really
isn't
supported
by
a
lot
of
the
open
source
projects,
and
so,
if
you
try
and
use
like
I,
actually
downloaded
and
compiled
not
compiled,
but
I
downloaded
and
modified
limbert
vagrant
to
run
on
M1.
A
So
libert
is
what
like
Fedora
ships
to
allow
liver
to
connect
to
with
bigger
you
do
bigger
up
instead
of
using
virtualbox
or
VMware,
which
is
two
of
the
standard
back
ends.
A
This
is
what
allows
you
to
patch
in
and
use
keyme
libert
as
your
back
end
patch,
that
to
work
on
the
M1
and
a
couple
other
folks
have
done
similar
things
and
we
got
to
get
to
work
as
long
as
you
do
a
force
install
of
the
ar-64
version
of
vector
when
you
install
background
through
Brew,
but
if
fault
installs,
the
x86
version
should
probably
show
this
share.
My
screen
desktop
two.
A
And
if
you
see
here,
I
have
changed
this
to
this.
This
is
amd64.
Oh
I
did
approve
update
today.
Okay,
so
just
blew
that
out,
but
you
can
change
this
to
the
ar-64
and
change
this
checksum
and
you
can
get
the
the
the
different
package
and
that
getting
this
is
AR.
64
is
what
will
allow
it
to
actually
invoke
the
correct
qmu.
A
The
problem
is
again
that
it
fails
and
it
fails
because
it
tries
to
that
tap
Network
and
it's
not
code
signed.
So
that's
kind
of
the
stopping
point
for
the
vagrant
libbert
stuff
right.
Somebody's
got
to
pay
up
for
the
code
signing
and
where
to
put
that
into
the
ecosystem
and
who's
going
to
cover
it
who's
going
to
pay
for
it.
A
It's
kind
of
the
big
question,
so
the
next
step
is
going
to
be
to
put
a
wrapper
around
UTM
and
their
applescript
and
get
that
into
a
to
a
bigger,
plug-in
and
I
think
the
way
to
do
that
is
going
to
be
to
take
the
current
work
and
the
liver,
Fork
that
and
then
modify
that
to
use
UTM
that
open
source
with
code
signing
for
that
uses.
Qmu
under
the
hood
virtualization
system-
so
that's
that's
kind
of
all.
A
I
got
that's
been
nine
days,
ish
worth
of
work,
trying
to
recover
my
workflow
on
M1
and
right
now
it
looks
like
it's
really
I.
Think
at
this
point
my
personal
thought
is
I'm
going
to
try
and
automate
standing
up
a
machine
in
gcp
for
right
now,
because
even
though
I
have
a
whiz,
bang,
64
gigs
of
memory
machine,
it's
basically
unusable
for
the
workflow
because
of
between
code
signing
and
firmware
challenges
and
stuff,
not
running
hypervisor
issues.
Plugins,
not
working.
A
There's
a
lot
of
work
to
be
done
to
make
it
work,
so
the
other
option
I
think
would
be
to
if
we
wanted
to
purchasing
a
license
for
VMware
would
immediately
skip
you
by
all
this
and
figure.
It
would
just
work
because
that's
our
that's
already
done!
That's
a
purchase
software
version,
so
there's
there's
no
open
source
and
I.
Don't
know
how
that
licensing
works
yeah!
A
That's
kind
of
the
sum
total
of
the
last
nine
days
of
my
life
and
that's
where
the
state
of
M1,
so
at
the
end
of
the
day,
a
single
virtual
machine.
Yes,
you
can't
access
it
from
the
outside
world,
it's
not
routable,
but
it
does
connect
to
the
Internet.
It's
too
not
only.
It
doesn't
stall.
You
can
install
gitlab
for
those
who
saw
my
post
to
ran
up
what
does
gitlab
look
in
the
text.
A
Browser
I
basically
accessed
the
standing
up
gitlab
through
a
links
text
browser
on
the
show
and
that
let
me
talk
to
the
instance
that
stood
up
to
make
sure
it
was
there.
I
could
log
in
which
is
laughably
funny
trying
to
use
gitlab
in
an
all
text
web
browser,
but
don't
laugh
if
it
works
right.
I
just
had
to
prove
that
it
was
there
and
I
could
log
into
the
setup.
So
yeah
other
questions
comments.
C
Yeah
so
at
the
beginning
you
were
indicating
that
that
podman
was
working,
I'm
curious
it
and
then
you
were
showing
you
know
and
Packer.
You
had
to
add
all
these
extra
Flags
to
quemoot
for
podman.
Is
it
just
like
that
they've
already
figured
out
like
you
mentioned,
impact
of
the
auto
detection
is
off
or
not
working
correctly
right,
so
is
it
more
than
like
pod
man's
auto
detection
was
working
and
setting
those
up
correctly.
A
Yeah
more
that
they
just
could
yeah
they
configured
it
all
like
they
specific.
They
explicitly
support
Mac
OS
with
podman
desktops,
okay,
so
they've
done
all
that
work
kind
of
under
the
hood,
so
yeah,
there's
there's
a
lot
of
fun
like
I.
Think
I
could
probably
cut
some
of
those
options
out
that
we
figured
out
like
as
I
look
at
it
more
it's
just
I'm.
A
What
I'm
weighing
up
is
you
know
my
time
in
digging
into
this
and
making
it
work
versus
I
actually
have
to
get
work
done
like
right
now,
I'm
in
this
state,
where
I
literally
cannot
do
about
half
of
the
reviews,
I
typically
would
take
because
I
S,
all
of
my
tooling,
all
of
my
setup,
is
all
a
local
virtual
machine
set
up
and
I
can't
even
initialize
a
virtual
machine
right
now
to
like
do
that.
A
Testing
on
an
automated
scale
like
I,
don't
have
x86
to
show
this,
but
let
me
see
if
I
can
show
this
like
when
I
test.
A
So
this
is
an
old
project
that
I
did
a
long
time
ago,
but
all
of
these
different
directories
are
different
methodologies
of
setup
where
there's
a
vagrant
file,
you're
you're,
not
sharing
your
screen
at
the
moment.
Sorry,
all
of
these
are
example
configurations
so
like
medium
is
like
like
one
plus
two
like
front
node
plus
database
plus
a
redis
right,
minimal
console
is
just
three
console
nodes:
external
nginx,
external
itis.
These
set
up
like
an
external
load
balancers
and
such
container
registry.
A
That's
exactly
what
it
sounds
like
tiny
is
for,
like
Pi
style
testing,
SC
Linux,
dice
Stig
is
for
like
testing
SC
Linux
under
very
constrained
purposes.
A
Apache
proxy
is
front
end
running
a
Docker
install
and
running
gitlab
and
Docker
also
get
lab
and
Docker
with
like
a
proxy
front
end,
because
we've
had
community
members
asked
about
that.
So
I
have
a
testing
framework
to
test
a
lot
of
things
that
have
just
come
up
and
I
have
a
gitlab
RB
that
auto
injects
it
auto
injects
SSL
and
templating
I
have
all
of
my.
My
local
lab
sets
up
all
the
DNS,
so
everything
just
works
I
can
do
full
sign
certificates
the
whole
the
whole
nine
yards.
A
All
of
this
is
unavailable
to
me
because
M1
basically
completely
blocked
it
and
that's
why
I'm
trying
to
get
there,
because
this
is
an
integral.
This
is
pretty
much
an
integral
part
of
my
workflow
to
be
effective
at
doing
what
I
do
so.
A
So
that
said,
that's
kind
of
that's
I
forget
which
original
question
with
CJ.
A
Oh,
the
you
already
answered
the
Pod
man,
sorry
in
that
in
that
kind
of
day,
obviously
more
coffee,
so
yeah.
But
at
this
point,
I
think
I
need
to
I've
been
trying
to
work
through
an
alternate
with
the
our
sandbox
there's
a
way
you
can
apply
terraform
templates,
but
the
temp.
The
temple
is
deeply
complicated.
A
I
spent
about
four
hours
last
night,
just
trying
to
figure
out
what
it
needed
for
me
to
stand
up
an
instance
and
it
just
I
couldn't
make
headers
tails
of
it.
So
I
gave
up
and
I'm
gonna
try
looking
at
it
again
today,
because
this
ability
to
stand
up
a
machine,
especially
for
a
good
example
of
this
one
of
my
primary
things
that
I
do
everything
I
test
every
time,
I
always
install
on
Enterprise,
Linux,
8
or
Enterprise,
Linux,
9
or
now
Enterprise,
79
and
the
reason
I
always
test
on.
A
That
is
that
we
don't
have
any
coverage
for
any
of
the
icy
Linux
distros.
So
whenever
I
get
an
MR,
I
always
run
all
the
testing
through
Enterprise
Linux
package,
because
then
I
see,
does
SC
Linux
work
and
I
kind
of
poke
around
extra.
Like
hey,
did
I
get
any
weird
SC
Linux
errors
did
anything
pop
out
at
me
anything
out
there,
that's
kind
of
something
I
just
do,
because
it
provides
coverage
to
that
side
until
we
get
the
approval
to
automate
it
and
pay
for
the
pipelines
for
it.
A
So
that's
kind
of
a
workflow.
That's
missing
now,
right,
like
so
I'm
going
to
convert
over
trying
to
use
gcp
and
get
that
set
up,
take
the
jobs
that
I
have
there
they're
configured
right
now,
they're
just
shell
scripts.
Let
me
convert
them
into
basically
ansible
template
jobs,
which
is
you
know
fairly
straightforward
too,
but
like
transform
them
over
and
put
them
into
gcp,
but
that's
probably
going
to
take
a
couple
of
days.
I
did
try
and
do
a
basic
terraform
because
of
the
the
pre-provised
template
is
way
too
complicated.
A
I
mean
it's
like
it's.
This
whole
laundry
list
of
variables
to
set,
but
you
don't
know
what
The
Faults
Are
they're,
not
clear,
so
I
just
try
doing
a
basic
one
and
I
got
permission
denied,
even
though
I
set
up
my
key
to
allow
me
to
do
provisioning.
So
that's
going
to
be
some
time,
I'm,
probably
going
to
reach
out
to
the
sandbox
Channel
and
be
like.
Is
there
a
more
straightforward
just
I
want
to
set
like
the
kind
of
like
we
do
set
the
domain
name.
A
I
said
the
distribution
of
the
Linux
distribution
and
move
forward,
because
there's
nothing
that
straightforward
available
right
now,
yeah
so
like
right
now,
as
far
as
I
as
far
I
can
tell
the
only
way
to
effectively
use
M1
for
tests
for,
like
actual
deep
testing,
is
to
pay
for
a
VMware
license,
because
the
tooling
around
UTM
is
just
not
there,
because
they
they
let
they've
likely
to
keep
it
very
close
to
the
Apple
ecosystem,
which
is
good
for
all
the
Apple
users.
A
But
it's
terrible
if
you
actually
want
to
orchestrate
a
large
number
of
containers
right
like
this.
You
know
the
the
laptop
that
I
have
I
explicitly
got
with
the
64
gigabytes
of
memory
and
the
extra
space
so
that
I
could
virtualize
up
to
10
or
12
or
15
machines
at
a
time,
because
that
is
actually
a
thing
that
I
have
done.
I'll
be
at
my
laptop
trying
to
set
itself
on
fire,
but
on
my
previous
Intel
laptop
I
would
set
up
10
virtual
machines
made
run
as
Mac
OS
got
more
and
more
bloated.
A
It
became
more
and
more
difficult
because
the
base
OS
takes
too
much
memory.
So
with
this
newer,
M1
I
was
hoping
to
Leverage
The
efficiencies.
Unfortunately,
between
the
lack
of
support,
we
just
got
the
qmu
support,
I
want
to
say
about
eight
months
ago.
You
could
get
it
if
you
compile
it
yourself
earlier,
but
it
didn't
release
to
the
while,
until
version
seven
code
signings
a
lack
of
bankrupting
support
which,
if
you,
if
you
do
install
vagrant,
make
sure
you
swap
over
to
the
ar-64
Because
by
default.
A
It
uses
x86,
which
will
look
for
x86
items
and
will
break
your
virtual
machines,
but
yeah
there's
just
a
whole
pile
of
challenges,
and
it's
actually
kind
of
surprising
to
me.
The
m1's
been
out
for
almost
two
years
now
and
the
community
hasn't
solved
a
lot
of
these.
So
there's
still
a
lot
of
kind
of
new
new
architectural
Growing,
Pains
I.
Think
a
lot
of
it
comes
down
to
Apple's
code.
A
So
it
sounds
like
there's
a
cat
here,
so
I
apologize
for
that
background
noise.
So
our
my
kitten's
mom
is
a
straight
still
straight
outside
she
won't
stay,
so
we
try
to
try
to
get
her
in
that
said,
that's
the
main
challenges
for
M1
right
now
is
that
we
just
Apple's
code
signing,
has
blocked
a
lot
and
then
also
the
open
source.
Community
does
typically
use
apple.
So
a
lot
of
that
support
like
it,
took
a
lot
of
time.
A
Bona
sites,
though
pogban
fully
supported
it,
does
work
for
those
who
use
pod
man.
It's
just
you
know
pop
that
machines
like
machine,
but
then
once
you're
in
you
can
do
your
typical,
like
podman
image,
LS,
just
any
Docker
command.
You
can
think
of
just
replace
it
with
podman
instead
of
Docker
and
it'll
work,
so
that
does
work.
A
So
if
you
have
a
container
workflow
that
does
sort
of
work,
caveat,
mtor
I've
got
to
sit
with
Jason
for
a
bit,
because
there
are
some
things
that
when
you
run
the
container,
for
whatever
reason
you
get
a
binary
mismatch,
it's
supposed
to
run
through
Rosetta.
It
doesn't
necessarily
so
that's
another
thing
that,
like
builds
gonna,
have
to
look
at
it's
getting
all
over
we're.
Looking
at
that
now
getting
all
the
containers
compatible
with
ar-64
there's.
A
And
lots
of
growing
pains
lots
and
lots
and
lots
of
growing
pains
any
other
questions.
C
Robert,
thanks
for
showing
showing
off
your
setup
there
and
giving
us
some
some
hints
and
places
to
look
for
for
those
of
us
who
might
want
to
try
this
or
are
thinking
of
ending
up
with
a
new
Mac
in
our
workflow
as
well.
A
A
If
you
want
to
do
just
a
single
stand-up
machine
that
works
fine,
if
you're
insistent
on
getting
an
M1
plan
to
work
in
gcp
and
don't
bother
with
the
extra
memory,
like
don't
waste
the
company
money
on
it,
that
is
kind
of
a
thing,
but
like
deep
down
I'm
kind
of
deeply
frustrated
by
if
I
had
known
it
was
going
to
be
this
many
other
things
and
that
you
know
it's
been
I
got
this
machine
in
July
and
I
have
been
kind
of
playing
with
it,
waiting
for
the
community
to
catch
up,
trying
to
tinkering
with
it
for
almost
a
year
now
and
yeah,
it's
just
not
ready.
A
So
if
you're
gonna
get
an
M1
get
the
least
smallest
thing,
you
can
get
get
away
with
and
plan
to
do
all
your
work
in
the
cloud
which,
unfortunately,
for
folks
like
when
it
rains
you
know
here
in
Florida,
internet
gets
flaky
I
know.
Baloo
has
some
of
the
same
problems
in
local
to
India.
The
internet
can
get
flaky.
So
if
you're,
if
you
have
very
flaky
internet,
the
M1
is
a
very
bad
choice,
because
a
lot
of
your
stuff
is
going
to
be
cloud-based.
A
If
you
don't
have
a
lot
of
that
kind
of
work
like
the
containers,
actually,
the
containers,
almost
just
they
kind
of
work
but
you're,
going
to
have
a
lot
of
problems
with
the
AR
and
the
translation
like
rosette
is
there,
but
it
doesn't
catch.
Everything
from
the
standpoint
of
the
container
and
part
of
that
is
because
the
command
line,
interface
and
Rosetta
don't
work
well
together,
like
Rosetta,
does
really
well
any
GUI
application
that
I've
tried
to
go
with
Rosetta
picks
it
up.
A
It
does
fine,
but
when
you
get
into
the
command
line
deep
into
the
command
line
underlying
things,
because
a
lot
of
these
are
done
through
either
configs
or
their
direct
catches
like
some
of
the
stuff
for
qmu,
you
can
configure
it,
but
some
of
it
under
the
hood.
It
does
detection
and
looks
for
like
oh,
what
was
it?
A
A
Oh
the
other
one.
If
you've
used
vagrant
in
the
past
on
Mac
OS,
newer
versions
of
Mac
OS
no
longer
allow
promiscuous
networking
on
the
Wi-Fi.
So
if
you're
used
to
setting
up
bridges
on
Wi-Fi
and
Mac
OS,
which
doesn't
work
in
your
Linux,
you
have
to
have
a
wired
connection.
Mac
OS
now
follows
what
Linux
does
so.
You
won't
be
able
to
kind
of
cheat
your
way
through
and
get
a
bridge
multiple
machines
using
a
promiscuous
network
mode
on
a
Wi-Fi
interface.
A
A
You
used
to
could
for
like
years
so
because,
before
my
work
back
here,
I
had
an
Intel
Mac.
That
I
did
the
same
kind
of
workflow
on
and
you
could
do
that
on
the
wireless,
whereas
on
Linux
you
have
to
have
a
network,
a
wired,
Hardware
interface,
to
do
that
bridging
so
there's
a
lot
of
little
Dodges
I!
Think
that's
why
I
kind
of
I
recommend
against
it.
If
you
have
a
virtual
machine
style
workflow,
the
M1
is
just
not
mature.
A
Unless
you
really
really
want
to
dig
deep,
like
go
really
deep
and
and
just
for
background
I
used
to
be
a
maintainer
for
the
grub2
project,
so
I
have
multiple
years
experience
in
bootloaders,
firmware
interfaces
and
I'm
finding
it
to
be
a
struggle.
So
just
caveat,
you
know,
buyer,
but
where
the
M1
is
not
ready
for
a
virtual
machine
workflow.
A
Unless
you
want
to
spend
another
I
think
it's
200
on
a
license
for
VMware.
This
VMware
works
with
background
out
of
the
box.
Apparently
supposedly
I.
Don't
know
that
I
want
to
ask
to
spend
that
much,
but
that's
worth
to
find
out
that
it
doesn't.
Then
the
money's
already
spent
right
but
yeah,
that's
that's
kind
of
where
it's
at
so
so
yeah
three
of
ten
would
not
recommend
the
M1
so
yeah,
that's
the
state
of
things.
So
maybe
I'll
do
this
again
another
year,
we'll
see
where
we're
at,
but
for
right.
B
Thanks
Robert
for
for
showing
off
the
demo
today
and
yeah
I
think
we
can
sign
off
here
all.
A
Right,
well,
thanks:
everybody
I
hope
you
all
benefit
from
the
benefit
from
the
the
diving
and
I
said.
If
anybody's
interested
in
this
stuff,
I
might
start
doing
like
maybe
an
hour
of
just
struggle
sessions
where
I
just
broadcast
it
never
wants
to
come.
We
can
kind
of
work
our
way
through
it
together,
because
I
know
there
are
a
couple
of
us
with
them
once
on
the
team.
A
Now
that
I
have
varying
levels
of
success
at
you
know,
the
big
one
I
think
is
going
to
be
getting
the
cloud
native
and
container
stuff
working
with
it,
because
for
that
it's
much
easier
to
test
local,
so
I
think
I
might
start
broadcasting
that
so
for
most
of
this
video
If,
you
see
me
advertising
for
that.
You
are
more
than
welcome
to
come
and
you
know
just
bring
a
pot
of
coffee
because
it's
it's
gonna
get.
It
gets
pretty
deep,
pretty
fast,
so
yeah,
but.
A
Have
a
great
it's
Thursday
have
a
great
rest
of
the
week
and
we'll
see
you
on
the
internet.
Bye.