Skip to content
New issue

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 VM is just created #1060

Open
1 of 5 tasks
Noksa opened this issue Jul 4, 2024 · 1 comment
Open
1 of 5 tasks

Provision scripts are ignored when VM is just created #1060

Noksa opened this issue Jul 4, 2024 · 1 comment

Comments

@Noksa
Copy link

Noksa commented Jul 4, 2024

Description

Provision scripts are ignored when we start VM first time (create it)

Version

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

Operating System

  • macOS Intel <= 13 (Ventura)
  • macOS Intel >= 14 (Sonoma)
  • Apple Silicon <= 13 (Ventura)
  • Apple Silicon >= 14 (Sonoma)
  • Linux

Output of 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

Reproduction Steps

  1. Add provision block in template as follows:
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
  1. Clean install VM
colima start
  1. Check that file is not present: colima ssh -- ls /etc/systemd/system/docker.service.d

  2. Stop and start again

colima stop && colima start
  1. Now file is present

Expected behaviour

Provision scripts should be considered when we do start first time

Additional context

As a workaround we can use colima start --edit but just save template without changes. In this case, scripts will be run

@davidolrik
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants