But that release never shows up in Activity (I can see up to v142) and I can see the code is actually not released to production by ssh-ing into the machine.
Deploys have been very unstable with Fly and itās making me reconsider if I should use something else. Itās a very critical feature for a developerās workflow.
This comes from the entrypoint trying to assign swap I believe. It was generated with the dockerfile generator. So it just seems it dies and does not show the failure anywhere else.
Iām not sure that has anything to do with fly. I did deploys on stage (nomad), prod (nomad), and then deployed roughly 100 times while testing out litefs on v2 apps to see how a migration would look.
Is this something new that youāre trying on an image?
Regarding activity, it doesnāt seem to show up for v2 apps consistently, which is definitely a fly thing.
This is the entrypoint generated for the dockerfile:
#!/bin/bash -e
if [ $UID -eq 0 ]; then
# allocate swap space
fallocate -l 512M /swapfile
chmod 0600 /swapfile
mkswap /swapfile
echo 10 > /proc/sys/vm/swappiness
swapon /swapfile
echo 1 > /proc/sys/vm/overcommit_memory
exec su rails $0 $@
fi
# If running the rails server then create or migrate existing database
if [ "${*}" == "./bin/rails server" ]; then
./bin/rails db:prepare
fi
exec "${@}"
That is a bit baffling as youāre in the if condition indicating this is running as root. The only explanation I can think of is that /swapfile already exists and is mounted?
#!/bin/bash -e
if [ $UID -eq 0 ]; then
# allocate swap space
if fallocate -l 512M /swapfile; then
chmod 0600 /swapfile
mkswap /swapfile
echo 10 >/proc/sys/vm/swappiness
swapon /swapfile
echo 1 >/proc/sys/vm/overcommit_memory
fi
exec su rails $0 $@
fi
# If running the rails server then create or migrate existing database
if [ "${*}" == "./bin/rails server" ]; then
./bin/rails db:prepare
fi
exec "${@}"
Donāt know if itās related, but Iām getting all deploys hanging on the final āPlacingā¦ā step. Seems to be happened to both my apps, but they both use the same Dockerfile so may well be something silly Iām doing too
2023-03-27T08:53:35.720 proxy[f64442fc] sin [warn] Failed to proxy HTTP request (error: no known healthy instances found for route tcp/443. (hint: is your app shutdown? is there an ongoing deployment with a volume or using the 'immediate' strategy? if not, this could be a delayed state issue)). Retrying in 1000 ms (attempt 30)
2023-03-27T08:53:45.818 proxy[f64442fc] sin [warn] Failed to proxy HTTP request (error: no known healthy instances found for route tcp/443. (hint: is your app shutdown? is there an ongoing deployment with a volume or using the 'immediate' strategy? if not, this could be a delayed state issue)). Retrying in 1000 ms (attempt 40)
2023-03-27T08:53:55.967 proxy[f64442fc] sin [warn] Failed to proxy HTTP request (error: no known healthy instances found for route tcp/443. (hint: is your app shutdown? is there an ongoing deployment with a volume or using the 'immediate' strategy? if not, this could be a delayed state issue)). Retrying in 1000 ms (attempt 50)
