We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provision scripts are ignored when we start VM first time (create it)
colima version 0.6.9 git commit: c3a31ed05f5fab8b2cdbae835198e8fb1717fd0f runtime: docker arch: aarch64 client: v27.0.3 server: v26.1.1 limactl version 0.22.0 qemu-img version 9.0.1 Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
colima status
INFO[0000] colima is running using macOS Virtualization.Framework INFO[0000] arch: aarch64 INFO[0000] runtime: docker INFO[0000] mountType: virtiofs INFO[0000] socket: unix:///Users/alexandr/.colima/default/docker.sock INFO[0000] kubernetes: enabled
provision
provision: - mode: system script: | cat <<EOF > /etc/systemd/system/docker.service.d/docker-buildkit-env.conf [Service] Environment="BUILDKIT_STEP_LOG_MAX_SIZE=20971520" Environment="BUILDKIT_STEP_LOG_MAX_SPEED=1048576" EOF systemctl daemon-reload systemctl restart docker
colima start
Check that file is not present: colima ssh -- ls /etc/systemd/system/docker.service.d
colima ssh -- ls /etc/systemd/system/docker.service.d
Stop and start again
colima stop && colima start
Provision scripts should be considered when we do start first time
start
As a workaround we can use colima start --edit but just save template without changes. In this case, scripts will be run
colima start --edit
The text was updated successfully, but these errors were encountered:
I too have this problem and the workaround does not work for me.
My custom provision section are never executed.
colima version 0.7.5 git commit: 1588c066b9ab9dae8205ef265929c7eb43dca473 runtime: docker arch: aarch64 client: v27.2.0 server: v27.1.1
Sorry, something went wrong.
No branches or pull requests
Description
Provision scripts are ignored when we start VM first time (create it)
Version
Operating System
Output of
colima status
Reproduction Steps
provision
block in template as follows:Check that file is not present:
colima ssh -- ls /etc/systemd/system/docker.service.d
Stop and start again
colima stop && colima start
Expected behaviour
Provision scripts should be considered when we do
start
first timeAdditional context
As a workaround we can use
colima start --edit
but just save template without changes. In this case, scripts will be runThe text was updated successfully, but these errors were encountered: