I modified some host kernel parameters, so you should now be able to use docker normally. Please try running a docker container and specify some port forwarding rules. If there are any errors, please reply with the docker start command and specific log information below.
If there are no issues, please reply with “no problem”.
There is no chicken here
isif Now it is also possible
look
I don’t have this machine
Just tried it, still cannot bind the port. Permission denied, can only use host mode
root@isif-9471:~/alpine# docker compose up -d
[+] up 4/4
[+] up 6/6 alpine:latest Pulled 6.7s
✔ Image alpine:latest Pulled 6.7s
✔ 1074353eec0d Pull complete 2.9s
✔ 644afed44dca Download complete 0.0s
✔ 5c1f58ba4e0d Download complete 0.0s
✔ Network alpine_default Created 0.2s
✔ Container alpine Created 0.8s
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 3: permission denied
root@isif-9471:~/alpine# cat docker-compose.yaml
name: alpine
services:
alpine-container:
image: alpine:latest
container_name: alpine
# network_mode: host
ports:
- "10031:22"
- "10032:10032"
tty: true
stdin_open: true
environment:
TZ: "Asia/Shanghai"
volumes:
- ./data:/data
restart: always
root@isif-9471:~/alpine# nano docker-compose.yaml
root@isif-9471:~/alpine# cat docker-compose.yaml
name: alpine
services:
alpine-container:
image: alpine:latest
container_name: alpine
network_mode: host
tty: true
stdin_open: true
environment:
TZ: "Asia/Shanghai"
volumes:
- ./data:/data
restart: always
root@isif-9471:~/docker# docker compose up -d
WARN[0000] No services to build
[+] up 1/1
✔ Container alpine Running
root@isif-9471:~/docker# docker exec -it alpine echo running
running
root@isif-9471:~/docker#
I just went online and tried uptime-kuma, but it still doesn’t work:
sudo apt-get update
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
sudo systemctl start docker
sudo systemctl enable docker
sudo usermod -aG docker $USER
newgrp docker
mkdir uptime-kuma
cd uptime-kuma
curl -o compose.yaml https://raw.githubusercontent.com/louislam/uptime-kuma/master/compose.yaml
docker compose up -d
root@isif-331f:~/uptime-kuma# docker compose up -d
[+] up 16/16
[+] up 18/18
islam/uptime-kuma:2 Pulled 278.5s
✔ Image louislam/uptime-kuma:2 Pulled 278.5s
✔ 66c528ee7b51 Pull complete 275.5s
✔ c236995d12f2 Pull complete 56.8s
✔ ce43fa88f43a Pull complete 90.6s
✔ ab9c5ae25e4d Pull complete 79.6s
✔ cc663995c53d Pull complete 80.7s
✔ 997b350cffa1 Pull complete 80.4s
✔ 17b86553b1c8 Pull complete 92.8s
✔ 5c32499ab806 Pull complete 56.1s
✔ c96d1635ad09 Pull complete 83.4s
✔ fe60297d5e1c Pull complete 92.9s
✔ b7f9c2a776ef Pull complete 93.0s
✔ 1cd175334932 Pull complete 233.1s
✔ 485f386a5929 Pull complete 233.4s
✔ 26fe02595b64 Pull complete 83.6s
✔ a4c0464bfa2e Download complete 0.0s
✔ Network uptime-kuma_default Created 0.3s
✔ Container uptime-kuma-uptime-kuma-1 Created 0.6s
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied
root@isif-331f:~/uptime-kuma#
Error:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied
The daemon returned an error response: creating container task failed: creating shim task failed: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file failure: reopen fd 8 failure: permission denied
There are still some issues, I will refine it again.
Received reminder Check it out
Thanks for sharing
It’s quite thoughtful. In virtual machines that are already containers, running containers again will definitely cause some issues with the network segment. I think we need to understand the principles of the network structure inside and outside Docker by looking at some tutorials before we can configure it. I believe we should set up some static routes on the container.
OK thanks
No need, it’s about container permissions. I made some modifications to the default configuration file, and it’s working now
ShareNL：Users using HZSG node note - Internet services / Announcements - NodeLoc
Tested and works
very much needed thank you
Received reminder! Come see, understand the cause and solution!