Unable to start rancher in single node

No idea what is going on, please help:

$ docker run -d --restart=unless-stopped
-p 80:80 -p 443:443
Unable to find image ‘rancher/rancher:latest’ locally
latest: Pulling from rancher/rancher
e7ae86ffe2df: Pull complete
7a7d9d161d19: Pull complete
50008eb40d82: Pull complete
a4c52b97fbb7: Pull complete
641ff91964f0: Pull complete
e7001d755da7: Pull complete
40a167ba4e08: Pull complete
87ec348b68d7: Pull complete
8794942a7d1f: Pull complete
b20146971f20: Pull complete
35ca8f361e21: Pull complete
05303c7fa324: Pull complete
e3d4f01866c6: Pull complete
f5936b6ead50: Pull complete
ac47af1edf76: Pull complete
ca14810a66ce: Pull complete
cbb83dcdc4fc: Pull complete
af6f8f1133bd: Pull complete
Digest: sha256:10e938f788e725d1d2ed7bc909bae8c7a83b756c520fb2596bf559e44e13587d
Status: Downloaded newer image for rancher/rancher:latest

$ docker ps
4e99d522cd2c rancher/rancher:latest “entrypoint.sh” 12 minutes ago Restarting (1) 31 seconds ago zen_murdock

$ http https://localhost

http: error: SSLError: HTTPSConnectionPool(host=‘localhost’, port=443): Max retries exceeded with url: / (Caused by SSLError(SSLEOFError(8, ‘EOF occurred in violation of protocol (_ssl.c:1129)’))) while doing a GET request to URL: https://localhost/

The output of docker logs 4e99d522cd2c will help here. And probably docker info.

Hi Seb:

$ docker info
 Context:    default
 Debug Mode: false
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  scan: Docker Scan (Docker Inc., v0.8.0)

 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 10
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
  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: d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version: de40ad0
 Security Options:
   Profile: default
 Kernel Version: 5.11.0-22-generic
 Operating System: Ubuntu 21.04
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 31.1GiB
 Name: faerun
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Experimental: false
 Insecure Registries:
 Live Restore Enabled: false

docker logs is an archive of 113K, i did not see a way to attach it. Anything in particular i should grep?

It should be repeating as it tries to start and can’t, so the last 10 lines or something before it exists would help. Otherwise, use pastebin.com or gist.github.com.

ok, here is the info:

$ sudo docker run -d -p 80:80 -p 443:443 --privileged rancher/rancher
$ docker ps
CONTAINER ID   IMAGE             COMMAND           CREATED         STATUS         PORTS                                                                      NAMES
d31839cea9ca   rancher/rancher   "entrypoint.sh"   7 seconds ago   Up 5 seconds>80/tcp, :::80->80/tcp,>443/tcp, :::443->443/tcp   wonderful_noyce
$ docker logs > /tmp/logfile.txt

Please find the file here:

i noticed that the log file did not include errors…

i redid the output with a better capture…
here is the gist:

It is probably because of

I0719 12:25:32.163200      51 conntrack.go:103] Set sysctl 'net/netfilter/nf_conntrack_max' to 524288
F0719 12:25:32.163217      51 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_max: permission denied

This was changed in a recent kernel, setting this manually on the host before starting the container or downgrading kernel (or using a supported OS, e.g. 20.04)