docker-compose fail to maintain up centos build

Im building a basic centos image with only some packages but Im forgotting something because finish well but not maintain the container. What Im doing bad?

docker-compose:

version: '3'
services:
  config_server:
    build: ../common/docker/ansible/.
    stdin_open: true
    volumes:
      - ../../api:/var/www/api
      - ../../server:/var/www/server
      - ../server/provision/server:/tmp/ansible
    working_dir: /tmp/ansible
    networks:
      net:
        ipv4_address: 172.28.0.10
    command: ansible-playbook playbook.yml

networks:
  net:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.28.0.0/24

Dockerfile:

FROM centos:7
RUN yum makecache && yum install -y epel-release wget
RUN yum install -y ansible

I would like to check If all tasks was well, and using:

docker logs 

I see logs from ansible script finishing well. But I don’t know why not maintains container with Exited (0) error

command used is

docker-compose up -d --build 

Suggestions?

Go to Source
Author: deconya

CentOS 8 guest in Hyper-V: mouse clicks not recognized but keyboard works

I’m running a CentOS 8 guest on Hyper-V in Windows 10. When I boot the virtual machine everything seems fine for a while. However, eventually the system stops recognizing mouse clicks. The mouse movement seems to be fine and I can switch to another virtual terminal and login, but clicking doesn’t do anything. I have a CentOS 7 guest on the same machine with no such problem. I’ve been searching but most of what I find online concerns other virtual machine environments or older versions of CentOS. How can I get to the bottom of this?

Go to Source
Author: antimeme

CentOS 8: Network Card disconnected on boot

Having an odd issue, just installed RockStore on a computer (CentOS based) and it is all running fine, but when the system boots the NIC is disabled.

I run nmcli device status and I can see the device is “disconnected”

If I then run nmcli con up DEVICEID the ethernet device connects fine, but if I reboot the system, the NIC is disabled again…

How can I force the card to connect automatically on boot?

Many thanks,

Mo

Go to Source
Author: PsychoMo

Docker, System has not been booted with systemd as init system (PID 1). Can’t operate

I am trying to create docker container for one of the centos service created by us.

We have 2 rpm files.

After installing on base image of centos 8.

I installed those 2 rpm files in it.

But, when I try to start the service, I am getting this error. when I ran
systemctl start <service_name>

System has not been booted with systemd as init system (PID 1). Can’t operate

Failed to connect to bus: Host is down

Based, on the feedback of different posts, I tried creating container with below steps.

docker run -it -p 8080:80 -p 16700:16700 centos

docker run -it -p 8080:80 -p 16700:16700 –privileged=true centos

Both same issue. Please suggest.

Go to Source
Author: Uday Kiran Reddy

Why I am unable to mount a CIFS from my server?

I have setup the samba on CENTOS 8 like that:

[global]
    workgroup = WORKGROUP
    security = user
    passdb backend = tdbsam

[e-table]
    path=/mnt/md0
    browseable=yes
    read only = no
    force create mode = 0660
    force directory mode = 2770
    valid users = lena

and /mnt has the following permissions:

$ ls -l /mnt
drwxrwxrwx. 27 lena lena 4096 Oct 18  2019 md0

But I get the following error on /var/log/samba:

[2020/06/16 17:46:15.738033,  0] ../../source3/smbd/service.c:784(make_connection_snum)
  make_connection_snum: canonicalize_connect_path failed for service e-table, path /mnt/md0

At the same time the client retrieves the following error:

error shown in client

So do you have any idea why that happens? Does affect that on the same time an huge rsync operation is performed on this file as well?

Go to Source
Author: Dimitrios Desyllas

How is a source RPM different from unpacking an RPM with rpm2cpio and cpio?

I am attempting to understand the use of a .srpm aka “source rpm” Red Hat Package Manager package. From what I understand so far, a .srpm is different from a standard .rpm in that it provides the source code and is commonly used during development. I am puzzled on why this is useful because if I run rpm2cpio ./myrpm-1.1-1.x86_64.rpm | cpio -idmv, I can still view the source code. As I understand, even standard RPMs pull down a .tar.gz/bz file which contains the source, and eventually builds this. Could you please clarify how source RPMs are different and why I would want to use one?

Go to Source
Author: the_endian