Cannot start Centos Docker image in 21.08-beta.1

pavel.belev

Cadet
Joined
Sep 26, 2021
Messages
1
I apologize beforehand if this has been posted or resolved, but I failed to find any useful information.

I am trying to add a Centos docker as an application in TrueNAS Scale 21.08-beta.1
I have the TrueNAS working properly with several storage Datasets.
I also installed PiHole from the Truecharts catalog without any issues.

When I try to install a Centos though it fails

Code:
Started container ix-chart
Back-off restarting failed container


Here is my container configuration
Code:
Application Name: centos-sandbox
Version: 2109.0.0
Docker Image:
Image repository: centos
Image Tag: latest
Image Pull Policy: Only pull image if not present on host
Add external Interfaces: 1
DNS Policy: Use Default DNS Policy where Pod will inherit the name resolution configuration from the node.
Host Path Volumes: 1
Security Context:
Privileged Mode: false
Update Strategy: Create new pods and then kill old ones


And here is the log:
Code:
2021-09-26 23:41:07    Scaled up replica set centos-sandbox-ix-chart-758d8f58f5 to 1
2021-09-26 23:41:07    Created pod: centos-sandbox-ix-chart-758d8f58f5-z5fxk
    Successfully assigned ix-centos-sandbox/centos-sandbox-ix-chart-758d8f58f5-z5fxk to ix-truenas
2021-09-26 23:41:09    Add eth0 [172.16.0.19/16] from ix-net
2021-09-26 23:41:15    Add net1 [192.168.0.103/24] from ix-centos-sandbox/ix-centos-sandbox-0
2021-09-26 23:41:15    Container image "centos:latest" already present on machine
2021-09-26 23:41:15    Created container ix-chart
2021-09-26 23:41:15    Started container ix-chart
2021-09-26 23:41:17    Back-off restarting failed container


I have relatively good knowledge in Linux and Docker, but my TrueNAS experience is fairly limited.
I would greatly appreciate if someone, who has any linux distro working in a docker in Scale could reply with step-by-step, or direct me to a working tutorila on how to achieve it.

My goal is to actually get a Centos with Gitlab in it, but the Gitlab part I can do later.
Thank you in advance.
 

Kris Moore

SVP of Engineering
Administrator
Moderator
iXsystems
Joined
Nov 12, 2015
Messages
1,471
Sounds like same issue as on this thread:

 

majinjing3

Dabbler
Joined
Sep 2, 2021
Messages
19
Try to get logs by "k3s kubectl -n xxx logs xxx", I think error maybe is in container logs.
 
Top