If you are trying to run the chainlink container with commands copied directly from the official guide, you might have included --link eth. This is not necessary when using EaaS, and will cause errors if you do not already have a container with that name.
Not reloading .env file
If you have updated the .env file with the EaaS variables, simply running docker start [container_name] is not going to load the new configuration. Start off by deleting the container with docker rm [container_name], then run the initial docker start command.Have you had a chance to answer the previous question?
We try to update this list as we are helping people setting up nodes. If your issue was not solved by anything we've mentioned on this page, feel free to send us an email to [email protected] or ask on Slack/Discord.