307750ff70
Docker does not respect the .dockerignore file when building from a tar. Instead by default we'll make a local clone into a tmp directory and build from there. Subsequent builds will reset the clone to match the checkout. Compared to building directly in the repo, we'll have reproducible builds. Compared to using a git archive: 1. .dockerignore is respected 2. We'll have faster builds - docker can be smarter about caching the build context on subsequent builds from a directory To build from the repo directly, set the build context to "." in the config. If there are uncommitted changes, we'll warn about them either being included or ignored depending on whether we build from the clone.
60 lines
1.2 KiB
Ruby
60 lines
1.2 KiB
Ruby
class Kamal::Commands::Builder::Native::Remote < Kamal::Commands::Builder::Native
|
|
def create
|
|
chain \
|
|
create_context,
|
|
create_buildx
|
|
end
|
|
|
|
def remove
|
|
chain \
|
|
remove_context,
|
|
remove_buildx
|
|
end
|
|
|
|
def info
|
|
chain \
|
|
docker(:context, :ls),
|
|
docker(:buildx, :ls)
|
|
end
|
|
|
|
def push
|
|
docker :buildx, :build,
|
|
"--push",
|
|
"--platform", platform,
|
|
"--builder", builder_name,
|
|
*build_options,
|
|
build_context
|
|
end
|
|
|
|
|
|
private
|
|
def builder_name
|
|
"kamal-#{config.service}-native-remote"
|
|
end
|
|
|
|
def builder_name_with_arch
|
|
"#{builder_name}-#{remote_arch}"
|
|
end
|
|
|
|
def platform
|
|
"linux/#{remote_arch}"
|
|
end
|
|
|
|
def create_context
|
|
docker :context, :create,
|
|
builder_name_with_arch, "--description", "'#{builder_name} #{remote_arch} native host'", "--docker", "'host=#{remote_host}'"
|
|
end
|
|
|
|
def remove_context
|
|
docker :context, :rm, builder_name_with_arch
|
|
end
|
|
|
|
def create_buildx
|
|
docker :buildx, :create, "--name", builder_name, builder_name_with_arch, "--platform", platform
|
|
end
|
|
|
|
def remove_buildx
|
|
docker :buildx, :rm, builder_name
|
|
end
|
|
end
|