spin provision using sudo password fails

[lucagrueninger]

Current Behavior

After configuring the .spin.yml file with "use_passwordless_sudo: false" and adding the password: in the users array I try to run spin provision.

First, an input "BECOME password: " pops up - I press enter without entering anything.
It then proceeds to run through until "TASK [Gathering Facts]" and fails with error:
"fatal: [server01.myserver.com]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: myusername@server01.myserver.com: Permission denied (publickey,password).", "unreachable": true}
"

Expected Behavior

I guess it should try to connect using root@server01.myserver.com as the user with myusername does not exist yet?

Steps To Reproduce

1. configure .spin.yml
2. spin provision

Environment

Spin Version: 
v3.0.0-beta2 [beta] (User Installed)

Operating System Version: 
ProductName:            macOS
ProductVersion:         14.6.1
BuildVersion:           23G93

Docker Info: 
WARNING: daemon is not using the default seccomp profile
Client:
 Version:    27.3.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1-desktop.1
    Path:     /Users/myusername/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7-desktop.1
    Path:     /Users/myusername/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/myusername/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     /Users/myusername/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/myusername/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/myusername/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/myusername/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/myusername/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/myusername/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.14.0
    Path:     /Users/myusername/.docker/cli-plugins/docker-scout

Server:
 Containers: 16
  Running: 3
  Paused: 0
  Stopped: 13
 Images: 20
 Server Version: 27.3.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.11-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 10
 Total Memory: 7.654GiB
 Name: docker-desktop
 ID: 32cecef7-8648-4a6a-ba9f-9443e1588cf5
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/myusername/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Anything else?

No response

[lucagrueninger]

Something I just noticed, a task prior to this throws a warning, don't know if this is related.

TASK [Create servers] ************************************************************************************************************************************************************************************************************************************************************************************
skipping: [localhost]
[WARNING]: Could not match supplied host pattern, ignoring: newly_created_servers

[jaydrogers]

@lucagrueninger: To confirm, this is a brand new server that you want to provision, correct?

Does this do anything different?

spin provision -u root

You might get the "BECOME PASSWORD" prompt, but I wonder if you can press enter through that?

[lucagrueninger]

@jaydrogers correct, it is a fresh server.
running it with "-u root" does fix it, the "BECOME password:" prompt also doesn't appear that way.
The command runs through and I was able to ssh using the myusername where I was then prompted to change the password.

[jaydrogers]

It was a documentation issue, thanks for pointing this out.

I updated the docs to be clearer 👍

fa2f10f