Latest builds failing about docker-mariadb

[aptalca]

I just pulled the latest and created a fresh container. No issues.

Is this a new container?
Please post a full log

[Dulanic]

There is no mysql log, but the container logs. 149 works fine.

stdout:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing... 

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30_config: executing... 
[cont-init.d] 30_config: exited 0.
[cont-init.d] 40-initialise-db: executing... 
Setting Up Initial Databases

stderr:

sed: can't read /etc/mysql/my.cnf: No such file or directory
sed: can't read /etc/mysql/my.cnf: No such file or directory
sed: can't read /etc/mysql/my.cnf: No such file or directory
sed: can't read /etc/mysql/my.cnf: No such file or directory
sed: can't read /etc/mysql/my.cnf: No such file or directory
sed: can't read /usr/bin/mysqld_safe: No such file or directory
ln: failed to create symbolic link '/etc/mysql/conf.d/custom.cnf': No such file or directory
/var/run/s6/etc/cont-init.d/40-initialise-db: line 60: mysql_install_db: command not found
/var/run/s6/etc/cont-init.d/40-initialise-db: line 5: mysqld: command not found

[Dulanic]

compose that works:

  mariadb:
    image: linuxserver/mariadb:149
    container_name: mariadb
    environment:
      - TZ=America/Chicago
      - PGID=1000
      - PUID=1000
      - MYSQL_ROOT_PASSWORD=nextcloud
    ports:
      - 3306:3306
    volumes:
      - /docker/containers/mariadb:/config
    restart: unless-stopped

compose that fails:

  mariadb:
    image: linuxserver/mariadb:150 #Or Latest
    container_name: mariadb
    environment:
      - TZ=America/Chicago
      - PGID=1000
      - PUID=1000
      - MYSQL_ROOT_PASSWORD=nextcloud
    ports:
      - 3306:3306
    volumes:
      - /docker/containers/mariadb:/config
    restart: unless-stopped

stdout when it works:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing... 

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30_config: executing... 
[cont-init.d] 30_config: exited 0.
[cont-init.d] 40-initialise-db: executing... 
Setting Up Initial Databases
Installing MariaDB/MySQL system tables in '/config/databases' ...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system


PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:

'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h bfcf5e8f0203 password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

You can start the MariaDB daemon with:
cd '/usr' ; /usr/bin/mysqld_safe --datadir='/config/databases'

You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr/mysql-test' ; perl mysql-test-run.pl

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

Database Setup Completed
[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
181218 12:58:20 mysqld_safe Logging to syslog.
181218 12:58:20 mysqld_safe Starting mysqld daemon with databases from /config/databases

[Dulanic]

Also, going into the container... only diff is me chaging 149 to 150:

dulanic@mediaserver:/opt$ sudo docker exec -it mariadb bash
[sudo] password for dulanic:
root@bfcf5e8f0203:/# mysql
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
root@bfcf5e8f0203:/# exit
exit
dulanic@mediaserver:/opt$ nano docker-c*
dulanic@mediaserver:/opt$ docker-compose up -d
portainer is up-to-date
quassel is up-to-date
vpn is up-to-date
tautulli is up-to-date
Recreating mariadb ...
rutorrent is up-to-date
Recreating mariadb
letsencrypt is up-to-date
jackett is up-to-date
nzbget is up-to-date
sonarr is up-to-date
radarr is up-to-date
radarr4K is up-to-date
Recreating mariadb ... done
Recreating nextcloud ...
Recreating nextcloud ... done
dulanic@mediaserver:/opt$ sudo docker exec -it mariadb bash
root@31ca8ce98a44:/# mysql
bash: mysql: command not found
root@31ca8ce98a44:/#

[sparklyballs]

i've created a container from :149 and :latest , and switched back and forth from both of them in all of the various combinations that are possible with no issues whatsoever.

i suggest removing any images or containers relating to mariadb and repulling to a sacrificial new volume for the config files and see for yourself...

[Dulanic]

Found issue, it was a corrupted issued I have to remove /w --force. Sorry guys! Have literally never ran into a corrupted image before!