Open cgsmith opened 3 years ago
Hi @cgsmith
do you still have issues with this?
@eugene-manuilov I moved back to VVV
Hi! I just installed 10updocker and I have the same issue.
Failed to automatically check for updates. Please ensure WP Local Docker is up to date.
Environment information
Device: ThinkPad W520
OS: Arch Linux
Kernel: 5.10.18-1-lts
I'm having the same issue. I installed 10updocker fresh on my machine, yesterday, and it started showing me this error since then.
Environment Info:
10updocker version: 2.8.1
docker info
gagan@enigma:~/Work/Local-Environment$ docker info
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
Server:
Containers: 35
Running: 35
Paused: 0
Stopped: 0
Images: 28
Server Version: 20.10.5
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
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 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 5.8.0-7642-generic
Operating System: Pop!_OS 20.10
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.21GiB
Name: enigma
ID: 4DGD:55JQ:IS2Y:XKK6:RGTC:WBGD:TOQU:7POK:CBSQ:WNTA:CUSU:T362
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: gagan0123
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
lsb_release -a
gagan@enigma:~/Work/Local-Environment/docker-test$ lsb_release -a
No LSB modules are available.
Distributor ID: Pop
Description: Pop!_OS 20.10
Release: 20.10
Codename: groovy
gagan@enigma:~/Work/Local-Environment/docker-test$ neofetch
///////////// gagan@enigma
///////////////////// ------------
///////*767//////////////// OS: Pop!_OS 20.10 x86_64
//////7676767676*////////////// Host: ROG Strix G531GT_G531GT 1.0
/////76767//7676767////////////// Kernel: 5.8.0-7642-generic
/////767676///*76767/////////////// Uptime: 34 days, 21 hours, 24 mins
///////767676///76767.///7676*/////// Packages: 2330 (dpkg)
/////////767676//76767///767676//////// Shell: bash 5.0.17
//////////76767676767////76767///////// Resolution: 1920x1080
///////////76767676//////7676////////// DE: GNOME 3.38.2
////////////,7676,///////767/////////// WM: Mutter
/////////////*7676///////76//////////// WM Theme: Pop
///////////////7676//////////////////// Theme: Pop-dark [GTK2/3]
///////////////7676///767//////////// Icons: Pop [GTK2/3]
//////////////////////'//////////// Terminal: gnome-terminal
//////.7676767676767676767,////// CPU: Intel i7-9750H (12) @ 4.500GHz
/////767676767676767676767///// GPU: Intel UHD Graphics 630
/////////////////////////// GPU: NVIDIA GeForce GTX 1650 Mobile / Max-Q
///////////////////// Memory: 10165MiB / 31963MiB
/////////////
~/.wplocaldocker/config.json
gagan@enigma:~/Work/Local-Environment/docker-test$ cat ~/.wplocaldocker/config.json
{"sitesPath":"/home/gagan/Work/Local-Environment","snapshotsPath":"/home/gagan/.wpsnapshots","manageHosts":true}
Added config.json because I am using custom sitePath, rest of the files are what comes default.
Not sure why the error was there in the first place, but my laptop wasn't powered off for over a month, and when I restarted it yesterday, the error went away.
Just an update, this error is still there, it just randomly creeps in and out. Earlier I thought restarting the system resolved it, but it didn't. Whenever the error is there, the command(any command) takes longer to execute as well.
I am also getting this error on the following system:
Fedora Linux 38 (Workstation Edition) Docker version 24.0.5, build ced0996 Node v18.16.1
It appears when I run any 10updocker command for the first time when booting.
Describe the bug After installing 10updocker on node 14.15.4 this error is displayed
Steps to Reproduce
10updocker
after fresh installExpected behavior
Not show a failure message
Environment information