Shreenidhi Shedi
Shreenidhi Shedi
I'm working on it.
This is done on Ph4 and above branches. Please close this issue.
Hi @prologic, Looks like there is some contention going on in your setup. cloud-init clean is being done before cloud-init finished running all stages. Also please attach your cloud config...
Can you give the cloud init log after using sleep 300 before clean? Also your userdata and cloud.cfg as I mentioned earlier?
I have a question for you: - path: /etc/docker/daemon.json Does `/etc/docker` directory exist upon first boot? I think not. Upon doing `systemctl start docker` - `/etc/docker` gets created. Give it...
Okay, my previous observation is not the cause. cloud-init will ensure that directory is present before writing file or else it will create directory. I used your sample yaml config...
I did the following: $ cloud-init clean $ systemctl stop cloud-init $ vmware-rpctool "info-set guestinfo.userdata $(cat config.yml)" $ systemctl restart cloud-init* One more hunch is, what if `tdnf -y update`...
Okay, I will give it one more shot. Please give the complete log using `cloud-init collect-logs` and attach the tarball here. And do this on a fresh instance of setup.
Try using `docker run --privileged ...`
Do `modprobe ip_tables` as root and then try docker rootless.