#Error whilst starting server.

95 messages · Page 1 of 1 (latest)

vagrant frigateBOT
#

@dusky python; Execute the commands below and post the output

sudo docker info | nc pteropaste.com 99
sudo snap list  | nc pteropaste.com 99
dusky python
#

Client: Docker Engine - Community
Version: 26.1.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.14.0
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.27.0
Path: /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 24.0.5
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc version:
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-31-generic
Operating System: Ubuntu Core 22
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.26GiB
Name: ns5019931
ID: 0afaf170-818e-47da-a3fb-041cf8315d14
Docker Root Dir: /var/snap/docker/common/var-lib-docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

Name Version Rev Tracking Publisher Notes
core22 20240408 1380 latest/stable canonical** base
docker 24.0.5 2915 latest/stable canonical** -
snapd 2.63 21759 latest/stable canonical** snapd

vagrant frigateBOT
dusky python
#

I have tried and it will not allow me to install it that way.

vagrant frigateBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

dusky python
cyan mesa
#

Remove the invalid mariadb repos you added and it should work

dusky python
#

Lowkey do not know how to do that. I installed it using ptero steps.

#

I haven't done sys admin work in 2 years so I haven't kinda lost my touch... Can you send me the command to do so please?

dusky python
#

I have unistalled it and tried to reinstall and exact same error does not have a release file.

dusky python
vagrant frigateBOT
#

I have found the following for: https://ptero.co/kanavamivi
@dusky python; Execute the commands below and post the output

sudo docker info | nc pteropaste.com 99
sudo snap list  | nc pteropaste.com 99
dusky python
#

It appears docker is getting mad

#

Error Event [360eafea-47d7-4eeb-9dbf-ab88d1cf59c7]: environment/docker: failed to run pre-boot process: environment/docker: failed to create container: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /var/lib/pterodactyl/volumes/60b62e98-ab45-4dc2-926a-d7161cd628a1

vagrant frigateBOT
#

@dusky python; Execute the commands below and post the output

sudo docker info | nc pteropaste.com 99
sudo snap list  | nc pteropaste.com 99
cyan mesa
#

they will be in the /etc/apt/sources.d/ folder most likely

dusky python
#

Do I have to ftp and do it???

#

Delete the files its throwing the error for?

cyan mesa
#

You will also need to remove the snap version of docker before installing the proper one.

cyan mesa
dusky python
#

Rip... I gotta go figure out snap. I did the snap because curl wouldn't work...

cyan mesa
#

but yes, delete the repo file that's throwing the error

#

off the top of my head. snap remove docker --purge

#

or it could be uninstall instead of remove

dusky python
#

purge worked

#

Error Event [ed9138a1-477d-4564-b7ba-dd6915cbfcc5]: environment/docker: failed to inspect container: Get "http://%2Fvar%2Frun%2Fdocker.sock/containers/60b62e98-ab45-4dc2-926a-d7161cd628a1/json": dial unix /var/run/docker.sock: connect: no such file or directory

vagrant frigateBOT
#

@dusky python: It looks like Docker probably is not running on your machine. Use systemctl status docker to check the status of it, and systemctl restart docker to get it operational again.

cyan mesa
#

Yep so now you need to get the proper version of docker installed

dusky python
#

The curl doesn't work for me

vagrant frigateBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

dusky python
#

idk why

#

it throws the same repo error

#

for mariadb

cyan mesa
#

So remove the broken mariadb repo

dusky python
#

Do I just fresh install mariadb?

cyan mesa
#

No? why would you do that

#

You need to remove the repo from apt

cerulean viper
#

this is an OS reinstall at this point

#

minimal - no docker install when installing OS, install it as per docs

dusky python
#

Why an OS reinstall?...

#

I did do it per docs.

#

It was working last night. Then got rebooted and stopped.

cerulean viper
#

well the docker snap version got installed somehow

dusky python
#

I could join the server and everything

#

I unistalled docker snap

cerulean viper
#

and it sounds like more got changed in your os

dusky python
#

the purge worked

cerulean viper
#

things dont just "stop working" for no reason

#

it sounds like your OS did an upgrade

#

or you did something that didnt take effect until reboot

#

either hunt down what changed in the reboot or reinstall OS

dusky python
#

No clue how to figure out what changed in reboot. Was even getting thrown the error before reboot with the repos

#

That's why we used snap

cerulean viper
#

then sounds like you are facing a reinstall of OS

#

otherwise you are going spin in circles like i've watched

dusky python
#

I can't even go in ftp and forcibly deleted snap?...

cerulean viper
#

reinstall OS.,....

dusky python
#

That's so frustrating. It will take hours to get ptero to be up and running again...

cerulean viper
#

we cant help any further from here as its getting into system issues

dusky python
#

Why did Danny suggest otherwise then?

cerulean viper
#

he was trying until you started not making sense

#

which explains how your OS got into an unknown state

#

may i ask how you installed the panel?

dusky python
#

I installed the panel with my sys admin friend in discord over screenshare and through the docs.

cerulean viper
#

there you go

#

you need your sysadmin friend

vagrant frigateBOT
#

You are expected to understand how to read documentation to use this Panel. We have spent many hours detailing how to install or upgrade our software. Please, take some time and read rather than copy and pasting and then complaining when things do not work.

If you expect to be able to install this with no understanding of basic linux system administration you should stop and turn around now

cerulean viper
#

^^^

#

bringing in a sysadmin friend to help means you now require their help any time when managing/maintaining the panel

#

it's complex, so you cant skip that part of learning how your OS works and the depenecies of the panel software such as mysql, redis, etc

dusky python
#

I have done it in the past plenty of times, it had been 2 years... I am just rusty with linux. Give me a sec I will tell you what part it doesn't like

#

It is the virtulization part

cerulean viper
#

what??

dusky python
#

systemd-detect-virt

#

none is the result

cerulean viper
#

ask your sysadmin friend please.

#

we cant teach you linux basics

dusky python
#

It's not that... You're treating me as if I am an idiot and have no clue of my background. It was the fact it says there's no virtualization which I didn't encounter in the past...

cerulean viper
#

none = good - so you are saying its "complaining" about a non issue. can you see why i'm telling you ask your sysadmin friend now...

dusky python
#

It throws an error there.

cerulean viper
#

so no, im not treating you like an idiot

dusky python
#

It would not allow me to do it using curl

cerulean viper
#

i'm stopping you from over reaching in support here

dusky python
#

I had to use snap.

cerulean viper
#

well reinstall your OS.

#

DONT use the snap version and get it working as per the docs say

#

as trying to go outside the docs puts you outside support here.

#

my intention is not to make you feel stupid but to curb your expectations of the support here.

dusky python
#

Sounds good, thanks. Sorry for being an annoyance.

#

I will reinstall OS.

#

Have a good one.

dusky python
#

Well, rebooted dedi and it started working. No clue why. Maybe it needed to be rebooted after purge of snap docker.

peak dock
#

help me