“Error: could not find driver”


#1

i had 3.x installed before
i followed the instructions
then installed php 7.2
and now i get this error message ““Error: could not find driver””

no apt-get issues
any ideas?


 root@txaqo:~# ee cli info
**Error:** could not find driver

root@txaqo:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

root@txaqo:~# docker info

Containers: 0

 Running: 0

 Paused: 0

 Stopped: 0

Images: 0

Server Version: 18.09.0

Storage Driver: overlay2

 Backing Filesystem: extfs

 Supports d_type: true

 Native Overlay Diff: true

Logging Driver: json-file

Cgroup Driver: cgroupfs

Plugins:

 Volume: local

 Network: bridge host macvlan null overlay

 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog

Swarm: inactive

Runtimes: runc

Default Runtime: runc

Init Binary: docker-init

containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39

runc version: 4fc53a81fb7c994640722ac585fa9ca548971871

init version: fec3683

Security Options:

 apparmor

 seccomp

Profile: default

Kernel Version: 4.15.0-43-generic

Operating System: Ubuntu 18.04.1 LTS

OSType: linux

Architecture: x86_64

CPUs: 2

Total Memory: 3.852GiB

Name: xxx

ID: NRYY:H2EM:EZAL:ALP3:VXLO:DEDA:CT3W:OI3T:NXMQ:CU7L:63NM:xxxx

Docker Root Dir: /var/lib/docker

Debug Mode (client): false

Debug Mode (server): false

Registry: https://index.docker.io/v1/

Labels:

Experimental: false

Insecure Registries:

 127.0.0.0/8

Live Restore Enabled: false

Product License: Community Engine

WARNING: No swap limit support

root@txaqo:~#

#2

Same problem. Help?


#3

conseguiu resolver ???


#4

Sim. Fiz um backup do servidor - pq estava em produção.

Aí atualizei tudo, apt update, apt upgrade.

Então reinstalei o EE:
wget -qO ee rt.cx/ee4 && sudo bash ee

Depois que reinstalei voltou tudo ao normal.
Não perdi nada dos sites que estavam rodando.


#5

the problem now is that
my current ee v3 setup has no database info
wordpress works
but this is what ee site info gives me

|DB_NAME||| deleted|
|DB_USER||| deleted|
|DB_PASS||| deleted|


#6

Nada funciona - ja pesquisei de tudo nada deu certo tem 3 dias que tou nessa to quase desistindo de usar o EE


#7

Mas o que está aconhescendo aí?


#8

Conseguiram resolver?


#9

just to update boils and ghouls,

i found a sqlite db editor (db browser for sqlite)
then I found the ee database sql from the server,
opened it manually
entered the user names and passwords and names of all the databases
and I was able to at least get ee working properly,

now im currently working on a new droplet for v4,

i must say though,
i’ve been using ee since like baaaack in the daaay son,
and the lack of support from devs, just because i missed the “v3 upgrade to v4” window of support…

note to devs:

i worked it out,
so please document this cumbersome workaround for the rest of us

much love
<3