Error deploying with Docker

[Elle]

@Hyperbytes

Lol @george, in wappler I have learned that "shouldn’t " means “shouldnt but might”

#bracingHerself

[George]

Aha ok I was confused by the logs indeed but those seems indeed from the development target.

So just to sum up the local development target is all working fine you can deploy the local server there with the database?

Maybe try to get this working first before creating a remote target.

Also it might be easier to just start fresh on a new project and get just things working one at the time.

Because if for example the base docker setup is not running well you might get many issues and vague errors and mess up a lot of project settings unnecessary while the error might be simple to solve initially.

So just try ste by step to get things done.

[Elle]

@George

Logs from Dev and DO produce the same error output.

What doesn’t make sense here is that, despite this, Dev deploys fine, DO produces the error.

I have started clean projects x 4, but will try again fresh… following @Hyperbytes videos while doing so.

And here my friends and family think I’m smart… so much for that… lol.

Thanks again for your input.

~Elle

[Hyperbytes]

Hmm, sorry, will check that out, not had that reported

[Elle]

No worries. I have headphones… when they’re charged.

I’m going to restart new project - take it from the top - while following your videos, and report the outcome. Appreciate you!

~Elle

[George]

Yes unfortunately docker can be sometimes pain to setup, normally it should go fine automatically but on some pc’s additional settings might be required.

And the problem is as long is it doesn’t run all fine you will be getting those weird errors

[Elle]

@George

I sure do wish I could figure out those “additional settings”

Sad face.

~Elle

[George]

Did switching off the use buildkit setting helped to solve the remote deploy error? Did you found that setting in the docker desktop settings?

[Elle]

@George

I did not. StackOverflow post showed a CLI command that I tried which didn’t work.

Then I got sidetracked with the log errors.

Do you have advice to turn off?

~Elle

[Hyperbytes]

@Elle

No worries. I have headphones… when they’re charged.

I’m going to restart new project - take it from the top - while following your videos, and report the outcome. Appreciate you!

Just checked, volume is a lillle lower than normal but still very clear.
Any problems, tell me, i can reauthor them easily if you feel there is a need, it they are poor for you then they probably are for everyone so need re-done

[George]

Hi Elle,

Seems like docker is just not working to you and you lost a lot unnecessary time to get it going.

Maybe a much more easier route was the one you got started with the lightweight development with the Wappler local server and SQLite and then for production combined with the railway app service see:

Railway App

After I posted the video on Image Optimisation, I wanted to deploy the finished app. Heroku is finished, as far as I am concerned. I then went ahead and tried various other hosts. The one that impressed me most is the newcomer on the block called Railway. Has a free tier, I opted for the developer tier which is free for the first $5. All I needed to do was to link my Github account to Railway and Railway did the rest. No fiddling around with NodeJS configurations, or any other config. The resul…

And definitely also review:

Resources and Tips for Beginners to Wappler

Intro This Guide This will be about getting started with Wappler when coming from a non-coding background. This isn’t a tutorial on how to make a site or anything (although those are linked), more talking about what’s involved and a general collection of resources I found useful. As a heads up, I am using ChatGPT to help with some of the explanations. This will just cover the basics you NEED to know, assuming you are able to learn more advanced stuff as you go. My Experience Just thought I’…

[Elle]

@Hyperbytes

I enjoyed the first video and the first ~9:00 minutes of the second. Confirming each step as directed along the way.

I was saddened when I was confronted with the same error on publish to DO:

This message persists, no matter what tutorial, instruction or video I refer to:
"listing workers for Build: failed to list workers: Unavailable: connection error: desc = “transport: failed to write client preface: write |1: file al
ready closed”

There must be an answer!

I was so filled with hope for Wappler just a few days ago.

I actually do quite well resolving complex problems; when I have an understanding of what the problem is. My frustration comes from my own lack of understanding of the issue. As well, needless to say it seems worrisome that seasoned Wappler’s are having the same frustration in trying to help me understand.

I appreciate your time and efforts nevertheless.

~Elle

[Apple]

At this point I think it might be worth trying an older Docker version on the DigitalOcean VPS.

Has anyone here deployed a DigitalOcean VPS through Wappler since the creation of this topic and verified no errors ocurr?

My workaround would be manually creating a DigitalOcean VPS with Ubuntu 22.04 and installing the docker.io package which is maintained by Ubuntu instead of Docker

[Teodor]

@Elle

I enjoyed the first video and the first ~9:00 minutes of the second. Confirming each step as directed along the way.

I was saddened when I was confronted with the same error on publish to DO:

Which video are you following? I tested the deployments to DO - just created a new server on Digital Ocean using the Resource Manager, then set up a new target using it and then deployed my project. Everything looks fine in my tests:

[Hyperbytes]

@Teodor I belive she was following my series on " Using the Resource Manager to create local and cloud droplets and databases with the aid of docker" on the wappler channel.

[Teodor]

Well i believe i’ve done the same.

1. Setup a server on DO in resource manager
2. Setup a remote target using this server
3. Deploy

Everything works correctly here.

[Elle]

@Teodor @Hyperbytes

Correct; the video series referenced earlier in this thread.

That’s awesome, Teodor. Happy to hear you got it working!

~Elle

[George]

Hi Elle,

If you are doing exactly the same thing and creating a brand new server in resource manager and then assign it to the remote target of your project but still the deploy of that target fails, can you make a short video of doing that? Maybe we can see then what is missing?

[tehowden]

I had some problem with deploying to Docker on Digital Ocean. I did do all the right things according to any video and instructions. The problem I find out, was that the firewall on my network stopped some of the traffic from the pc and to Digital Ocean and back again. I dont know wy it did that, but an update on the firewall and what it stopped fixed the problem.
Just a small tips.

And by the way have you tried some of the other provider like Hetzner or Linode.

[Elle]

@Hyperbytes @tehowden @kfawcett

So… after about a week of frustration, I resolved this in about 30 minutes by changing from DO to Heroku.

At least I can deploy the app on Heroku and still take advantage of the DO db clusters that I’m fairly familiar with already.

Thank you so much for everyone that posted in attempt to get me to a resolution. It’s appreciated.

~Elle