pythoninthegrass
commented
6 days ago Ditto the docker network:
[STDERR] Error response from daemon: network with name sidekick already exists
panic: error running command - sudo docker network create sidekick: - Error response from daemon: network with name sidekick already existsFWIW these are the steps needed to fix them manually after logging in as another user with sudo privileges:
sudo -s
systemctl stop nginx
systemctl disable nginx
sed -i 's/PermitRootLogin no/PermitRootLogin yes/' /etc/ssh/sshd_config
systemctl restart ssh
cd /home/sidekick
docker compose -f docker-compose.traefik.yml down --remove-orphans
userdel sidekick
rm -rf /home/sidekick
docker network rm sidekickAnd finally I'm left with this error:
[STDERR] Container sidekick-traefik-service-1 Starting
panic: error running command - cd sidekick-traefik && sudo docker compose -p sidekick -f docker-compose.traefik.yml up -d: - Container sidekick-traefik-service-1 Starting
goroutine 1 [running]:
github.com/mightymoud/sidekick/cmd.init.func4(0x140001ec900?, {0x104cdd572?, 0x4?, 0x104cdd576?})
/Users/lance/git/sidekick/cmd/init.go:191 +0x1bec
github.com/spf13/cobra.(*Command).execute(0x10515acc0, {0x1051c78e0, 0x0, 0x0})
/Users/lance/.asdf/shims/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:989 +0x828
github.com/spf13/cobra.(*Command).ExecuteC(0x10515b560)
/Users/lance/.asdf/shims/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117 +0x344
github.com/spf13/cobra.(*Command).Execute(...)
/Users/lance/.asdf/shims/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041
github.com/mightymoud/sidekick/cmd.Execute()
/Users/lance/git/sidekick/cmd/root.go:36 +0x24
main.main()
/Users/lance/git/sidekick/main.go:20 +0x1c
exit status 2It'd probably be easier to rename the compose file to docker-compose.yml; then the -f flag wouldn't be necessary. Not sure why it's got a non-standard name if there aren't multiple files in the repo/directory.
MightyMoud
lpil
First, wanna make sure you know I really appreciate what you're doing here. OSS is oftentimes a thankless vacuum and it can be really frustrating at times. So kudos to you @MightyMoud!
Was able to figure out what's going on with the SSH connection to my Ubuntu box. macOS doesn't really use the SSH agent (that I'm aware of) like *nix distros.
Refactored quite a few of the cmd and utils scripts to read the .env file of my private key successfully.
However, ran into some other gotchas where
I'm confident in my linux/dev abilities to fix all the above, but honestly, the error should've been handled in the business logic already.
The alternative is blowing away the vm and starting from scratch which is trivial on VPSes but a bit of a pain in a homelab environment (although a type 1 hypervisor and cloud-init helps!).
I say all that to give constructive feedback. I like the project and it's novel approach to real world problems. Know we all have blind spots and end users' environments can differ quite a bit.
Happy to help QA 🤙