kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
frigginglorious has quit [Read error: Connection reset by peer]
NwS has joined #sandstorm
prompt-laser has joined #sandstorm
NwS has quit [Quit: See you in Isla de Muerte!]
_whitelogger has joined #sandstorm
prompt-laser has quit [Quit: Connection closed for inactivity]
frigginglorious has joined #sandstorm
frigginglorious has quit [Ping timeout: 246 seconds]
frigginglorious has joined #sandstorm
nicoo has quit [Remote host closed the connection]
nicoo has joined #sandstorm
frigginglorious has quit [Ping timeout: 260 seconds]
<abliss>
i'm having a problem with vagrant-spk on buster where every time I try to provision a new VM, it gets stuck waiting for input configuring openssh. Despite me attempting every way I can to make it noninteractive . anyone solved this already?
<abliss>
oh, hm, I think that before my setup.sh script even happens, there's an apt-get upgrade going on that lacks the right flags
<abliss>
oh yeah it's in global-setup.sh
<isd>
That would do it.
<isd>
Did you modify that file?
<abliss>
no, but i'm probably using an old one created by vagrant-spk init that was targeting strech, and i manually changed to buster afterwards
<isd>
If you do vagrant-spk setupvm the call to upgrade in that file has a -y.
<isd>
Maybe upgradevm would have fixed it.
<abliss>
yeah, -y isn't enough anymore apparently. you need bigger guns: `apt-get upgrade --yes --force-yes -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"`
<abliss>
otherwise the upgrade of openssh complains about some locally-changed config file and wants interactive resolution of the conflict
<isd>
Ok, so we'll have to address that when we upgrade the Vagrantfile upstream.