Menu

flisk up Treats Goose Like Every Other BYO App
📰

flisk up Treats Goose Like Every Other BYO App

DEV Community: docker·flisk·about 4 hours ago
#VfM3RjPB
#devtodocker#devto#dev#flisk#container
Reading 0:00
15s threshold

Part 4 of Any language on Flisk. The BYO doc says docker run is not enough. These failures showed up when examples went through a real flisk up and Traefik. They are not Goose-specific.

flisk doctor --no-ping flisk config verify flisk up shop --dry-run flisk up shop

Enter fullscreen mode

Exit fullscreen mode

A cold cache is slow. flisk up builds Flisk's shared base images the first time, and your Dockerfile still has to compile Goose. Give the first check several minutes. Then curl the URL --dry-run printed:

curl -fsS http://api.<project>.localhost/api/goose/health

Enter fullscreen mode

Exit fullscreen mode

Expect {"status":"ok"} .

Failures the doc already recorded

What breaks What you see Fix in the app, not in Flisk

Bind 127.0.0.1 Container runs. Traefik never gets a 200. Bind 0.0.0.0 . Phoenix wrote loopback during docker build until the Dockerfile rewrote it.

Host allowlist Blocked-host response. Rails did this. Allow api.<project>.localhost , or any host.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.