You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Results:
After to create the statefulset (with implicit PersistentVolume and PersistentVolumeClaim that aren't in the tutorial). the replica of the pod mysql-0 won't to be created and will report CrashLoopBackOff status with the log below:
$ kbk logs pod/mysql-0
Error from server (BadRequest): a container name must be specified for pod mysql-0, choose one of: [mysql xtrabackup] or one of the init containers: [init-mysql clone-mysql]
But when I tried to change default iptables forward (running iptables -P FORWARD ACCEPT on the node - virtualbox VM) nothing happed and still persists. I try to disable ufw firewall to, but again, persists.
The text was updated successfully, but these errors were encountered:
mayconfsbrito
changed the title
iptables foward doesn't work for mysql replicated stateful application
iptables forward doesn't work for mysql replicated stateful application
Sep 18, 2018
RKE version: v0.1.10-rc2
Docker version: (
docker version
,docker info
preferred)Containers: 70
Running: 26
Paused: 0
Stopped: 44
Images: 16
Server Version: 17.03.2-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 227
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-35-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.914 GiB
Name: ubuntu-rke-1
ID: VLIA:XYZ4:6QYJ:AQUF:ESH4:OHIE:ICRU:2CPI:5QAI:6633:5QHD:NPF4
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
192.168.101.181:5000
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Ubuntu Server 18.04 (Bionic)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
VirtualBox
cluster.yml file:
Steps to Reproduce:
Make the tutorial Run Replicated Stateful Application of k8s docs.
Link to docs:
https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/
Results:
After to create the statefulset (with implicit PersistentVolume and PersistentVolumeClaim that aren't in the tutorial). the replica of the pod mysql-0 won't to be created and will report CrashLoopBackOff status with the log below:
I've discovered that this is a bug of docker with IPTABLES in the node host and are specified in Upgrading docker 1.13 on nodes causes outbound container traffic to stop working issue of kubernetes.
But when I tried to change default iptables forward (running
iptables -P FORWARD ACCEPT
on the node - virtualbox VM) nothing happed and still persists. I try to disable ufw firewall to, but again, persists.The text was updated successfully, but these errors were encountered: