Open Noksa opened 2 weeks ago
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
Now file is present
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
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
Now file is present
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 run