[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: mariadb-container gets AVC on up-to-date centos



Which centos?  There's a couple of known overlay bugs that may be at
fault, one with unix domain sockets not working at all, one with
selinux and file systems.  There are a few others known.

We aren't officially supporting overlay until 7.4, mostly due to those
and other bugs.

> On Mar 10, 2017, at 5:23 AM, Tobias Florek <openshift ibotty net> wrote:
>
> Hi,
>
> I am running into the following AVC on CentOS
> origin-node-1.3.3-1.el7.x86_64
> docker-1.12.6-11.el7.centos.x86_64
> selinux-policy-targeted-3.13.1-102.el7_3.15.noarch
> selinux-policy-3.13.1-102.el7_3.15.noarch
>
> using Overlay2 storage driver
>
> type=AVC msg=audit(1489140803.413:12054): avc:  denied  { write } for
> pid=93560 comm="mysqladmin" name="mysql.sock" dev="dm-1" ino=35119929
> scontext=system_u:system_r:svirt_lxc_net_t:s0:c12,c13
> tcontext=system_u:object_r:container_share_t:s0 tclass=sock_file
>
>
> When mariadb is started with
> mysqld --disable-networking --socket=/tmpj/mysql.sock
> mysql client cannot connect to /tmp/mysql.sock because of the AVC:
> mysql -u root --socket=/tmp/mysql.sock
>
>
> Is that a known bug, if not, where should I report it?
>
> Cheers,
> Tobias Florek
>
> _______________________________________________
> users mailing list
> users lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]