[hadoop@hadoop03 fastdfs-docker]$ sudo docker run -d --privileged=true a:v1
2be67a4f7e63d5277fc7bea8ca46946e40d526f93bc634166826de2bd5179554
[hadoop@hadoop03 fastdfs-docker]$ sudo docker exec -it 2b bash
[root@2be67a4f7e63 /]# service keepalived start
Redirecting to /bin/systemctl start keepalived.service
Failed to get D-Bus connection: Operation not permitted
[root@2be67a4f7e63 /]# exit
exit
[hadoop@hadoop03 fastdfs-docker]$ sudo docker stop 2b
2b
[hadoop@hadoop03 fastdfs-docker]$ sudo docker rm 2b
2b
Create a container and start with/usr/SBIN/init
######################
[hadoop@hadoop03 fastdfs-docker]$ sudo docker run -d --privileged=true a:v1 /usr/sbin/init
2dfab2702a180537f58549457fd5993bb0ee3e6e2da72e0672af58d922286ffd
[hadoop@hadoop03 fastdfs-docker]$ sudo docker exec -it 2d bash
[root@2dfab2702a18 /]# service keepalived start
Redirecting to /bin/systemctl start keepalived.service
[root@2dfab2702a18 /]#
[root@2dfab2702a18 /]# service keepalived status
Redirecting to /bin/systemctl status keepalived.service
● keepalived.service - LVS and VRRP High Availability Monitor
Loaded: loaded (/usr/lib/systemd/system/keepalived.service; disabled; vendor preset: disabled)
Active: active (running) since Fri 2021-10-08 06:26:55 UTC; 4s ago
Process: 250 ExecStart=/usr/sbin/keepalived $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 251 (keepalived)
CGroup: /docker/2dfab2702a180537f58549457fd5993bb0ee3e6e2da72e0672af58d922286ffd/system.slice/keepalived.service
└─251 /usr/sbin/keepalived -D
‣ 251 /usr/sbin/keepalived -D
Oct 08 06:26:55 2dfab2702a18 systemd[1]: Started LVS and VRRP High Availability Monitor.
Oct 08 06:26:55 2dfab2702a18 Keepalived_vrrp[253]: Unable to load module xt_set - not using ipsets
Oct 08 06:26:55 2dfab2702a18 Keepalived_vrrp[253]: VRRP_Instance(VI_1) removing protocol VIPs.
Oct 08 06:26:55 2dfab2702a18 Keepalived_vrrp[253]: VRRP_Instance(VI_1) removing protocol iptable drop rule
Oct 08 06:26:55 2dfab2702a18 Keepalived_vrrp[253]: Using LinkWatch kernel netlink reflector...
Oct 08 06:26:55 2dfab2702a18 Keepalived_vrrp[253]: VRRP_Instance(VI_1) Entering BACKUP STATE
Oct 08 06:26:55 2dfab2702a18 Keepalived_vrrp[253]: VRRP sockpool: [ifindex(447), proto(112), unicast(0), fd(10,11)]
Oct 08 06:26:55 2dfab2702a18 Keepalived[251]: Keepalived_healthcheckers exited with permanent error FATAL. Terminating
Oct 08 06:26:55 2dfab2702a18 Keepalived[251]: Stopping
Oct 08 06:26:56 2dfab2702a18 Keepalived_vrrp[253]: Stopped
[root@2dfab2702a18 /]#
Read More:
- Docker CentOS Failed to get D-Bus connection: Operation not permitted
- linux docker Error Failed to get D-Bus connection: Operation not permitted
- Failed to start docker.service : unit not found
- ADB remount failed: operation not permitted
- systemctl start docker Job for docker.service failed because the control process exited with error
- Failed to get D-Bus connection: No such file or directory
- java.net.SocketException: socket failed: EPERM (Operation not permitted)
- Job for docker.service failed because the control process exited with error code. See systemctl sta
- Keepalived add service self-start error analysis [How to Solve]
- EPERM: operation not permitted, symlink ‘../../’
- After adb is connected to an android phone, remount failed: operation not permitted when adb remount is a roundabout solution
- NPM install Error: EPERM: operation not permitted, mkdir solution
- [Vue] install vuex, error: eperm: operation not permitted, rename
- AVD FFmpeg avcodec_ A solution of open2 returning – 1 (operation not permitted)
- npm ERR Error: EPERM:operation not permitted, rename
- Solve win10 docker:error during connect: Get https://192.168.99.100 : 2376 and error checking TLS connection
- “NPM err! Error: eperm: operation not permitted” problem solving
- npm ERR! Error: EPERM: operation not permitted, open ‘C:\Program Files\nodejs\node_ Solution to cache / xxx
- docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled
- MongoDB Error: Failed to start mongod.service: Unit mongod.service is not loaded properly