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
Sometimes, my Lenses Box container will fail to start again after being stopped, with an error /var/www/config/run already existing. The only thing I can then do is remove the container and start over again.
▸ ~ docker container start -a lenses-dev
Setting advertised host to 127.0.0.1.
Broker config found at '/var/run/broker/server.properties'. We won't process variables.
Connect worker config found at '/var/run/connect/connect-avro-distributed.properties'. We won't process variables.
Schema registry config found at '/var/run/schema-registry/schema-registry.properties'. We won't process variables.
REST Proxy config found at '/var/run/rest-proxy/kafka-rest.properties'. We won't process variables.
Zookeeper config found at '/var/run/zookeeper/zookeeper.properties'. We won't process variables.
Lenses conf config found at '/var/run/lenses/lenses.conf'. We won't process variables.
Lenses security conf config found at '/var/run/lenses/security.conf'. We won't process variables.
ln: failed to create symbolic link '/var/www/config/run': File exists
The text was updated successfully, but these errors were encountered:
This issue turned out to be different than the one I fixed earlier. The problem only showed at the second restart of the container, so it escaped my testing.
I just pushed a fix: lensesio/fast-data-dev@460db5b
It will take about an hour for the docker image to become available at the docker hub. Hope everything is ok now. :)
I reported an issue in the
#lenses
Slack channel about this and @andmarios committed a fix. However, I may have prematurely declared it fixed. I'm still running into the problem, but it seems to happen randomly.Sometimes, my Lenses Box container will fail to start again after being stopped, with an error
/var/www/config/run
already existing. The only thing I can then do is remove the container and start over again.The text was updated successfully, but these errors were encountered: