flannel-docker-opts.service produces empty flannel_docker_opts.env #1801
Comments
This was fixed in 1248.0.0. |
Could this be backported to stable, please? |
Stable is 1298.5.0, so this should be fixed in all channels. Let us know if that is not the case. |
@dm0- I don't think 1298.5.0 has this fixed
It looks like |
@dm0- thx, I also found this after comment. But we still this issue (specially at slow environments like vagrant, where pulling flannel image take time)
and you can see that
|
I can't reproduce that behavior. Did you copy any service files into |
@dm0- yes we have
|
What does |
|
Okay, can you open a different bug? Those units have the correct ordering, and I couldn't reproduce the problem with them. |
1298.7.0 and this is still an issue. |
Issue Report
Bug
Container Linux Version
Environment
What hardware/cloud provider/hypervisor is being used to run Container Linux?
bare-metal
Expected Behavior
flannel-docker-opts.service
should succeed and/run/flannel/flannel_docker_opts.env
should not be empty.Actual Behavior
/run/flannel/flannel_docker_opts.env
is empty.Reproduction Steps
/etc/systemd/system/docker.service.d/40-flannel.conf
Other Information
It should probably be
flanneld.service
.My assumption is that
flanneld.service
, which should be startedBefore=flannel-docker-opts.service
, somehow is not yet up when the latter starts, hence/run/flannel/subnet.env
is not yet present and thus/run/flannel/flannel_docker_opts.env
is not filled with anything.Later, when I log into the node,
/run/flannel/subnet.env
contains values forFLANNEL_NETWORK
,FLANNEL_SUBNET
, as well asFLANNEL_MTU=1500
andFLANNEL_IPMASQ=true
. The latter should have caused/opt/bin/mk-docker-opts.sh
fromquay.io/coreos/flannel:v0.6.2
to writeDOCKER_OPT_IPMASQ="--ip-masq=false"
. Since this was not written, I must assume$FLANNEL_IPMASQ
was missing from/run/flannel/subnet.env
, when/opt/bin/mk-docker-opts.sh
looked at it.The text was updated successfully, but these errors were encountered: