Error deploying with Docker

Wappler General
61

Elle
Try deploying to development target. Sometimes the libraries are present but not running in the docker container. Deploy to development will refresh the files

1 Like
63

@Hyperbytes

Deployment to dev is fine. It’s the deploy to DO that fails. Just tried again without success.

~Elle

64

@Notum

Thanks for the response. Here is the output:

image

~Elle

65

But deploy to production effectively replicates the dev environment to production. If development is wrong, then production will also

66

@Hyperbytes

Thanks for the response. Agreed; what you say makes a lot of sense.

Yet, here I am. Sad face.

~Elle

67

You running docker under WSL or in a HyperV container?

68

@Hyperbytes

wsl

~Elle

69

:+1:that’s good news anyway

1 Like
70

@Hyperbytes

It’s the Docker log output I posted above that has me concerned. It seems to me it should not be throwing errors? The clue must be in there, no?

~Elle

71

And by the way… I feel a bit ashamed that something like setting up the environment has taken me two days and counting.

It’s almost… surreal.

~Elle

72

The clue is in the calls to missing files which should be present in your docker container. That’s why I thought they may be missing from your local container file content.

73

@Hyperbytes

Exactly! But they apparently are not.

~Elle

74

Seems to me like you are running into multiple issues, is the one above solved at least?

75

Lol,you are not the first, probably won’t be the last. You will probably be even more frustrated when it turns out to be a simple config issue which was missed in an early stage.
Nothing in my videos which gave you any clues where you went wrong?

76

If all local docker things works fine then there shouldn’t be any WSL or docker issues @Hyperbytes

77

@George

Thanks for the response.

It is not.

“Multiple issues” is worrisome. Here I thought I had just the one:

image
image1399×195 13.3 KB

~Elle

78

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

1 Like
79

But if this is still going on you should be able to publish to digital ocean at all, so I was wondered how you got anything there at all.

80

@Hyperbytes

I have not yet watched your videos. I tried, but the volume was such that I was not able to hear even with my laptop speakers at 100%. Reached for my Bose headphones and they were not charged. Put them on the charger and will begin watching today.

Appreciate you!

~Elle

81

@George

That’s just it! I haven’t!

It deploys to dev fine. On DO publish it fails.

Also intriguing is when I look at the Docker logs after realizing there are separate logs for DO & Dev, Dev produces the same error output as DO, yet publishes 200.

~Elle