IPv6 localhost not supported #583

ujwal-setlur · 2023-01-15T03:37:19Z

Description

Hi,

I am using node 18 on OS X Ventura 13.1, and the pg client resolves localhost to ::1 which Colima cannot handle. The connection fails. If I use 127.0.0.1, it works. I believe this is because node 18 does enforce IPv4 resolution first anymore, and Colima cannot handle a IPv6 address. But Docker Desktop handles it just fine. Any chances of getting this addressed?

Thanks!

Version

Colima Version: 0.5.2
Lima Version:
Qemu Version:

Operating System

Output of `colima status`

No response

Reproduction Steps

Fire up Postgres container.
Run node 18 code to connect to it via localhost. It will resolve to ::1 (IPv6)
Connection failure

Expected behaviour

Should connect.

Additional context

Docker Desktop works.

The text was updated successfully, but these errors were encountered:

henrik242 · 2023-01-30T15:19:50Z

You can work around this by commenting out ::1 localhost in /etc/hosts. Not the best solution, but better than nothing..

SEO: We had this problem when using testcontainers-node. Error: Failed to connect to Reaper and Error: No Docker client strategy found wasn't straight forward to debug. Setting TESTCONTAINERS_HOST_OVERRIDE=127.0.0.1 also works.

henrik242 · 2023-01-30T16:49:45Z

Maybe related: lima-vm/lima#1330

shlomioz · 2023-02-12T09:29:37Z

Same issue for me.

mxngls · 2023-02-24T09:41:36Z

Not quite sure if thats exactly related, but I had the same problem while connecting a local node application to a (locally running) docker container. What helped in my case was to specify the socket option when creating the Redis client:

export const redisClient = redis.createClient({
  // url: process.env.REDIS_URL,
  socket: {
    host: "127.0.0.1",
    port: 6379,
  },
  legacyMode: true,
});

When using Docker Desktop this setup was not necessary.

sabberworm · 2023-03-09T20:50:38Z

You can work around this by commenting out ::1 localhost in /etc/hosts. Not the best solution, but better than nothing..

This did not work for me. I suspect the resolution of localhost is done by some clients without going through the hosts file.

What did work was manually changing all connection strings to reference 127.0.0.1 instead of localhost.

I agree, though, that the real fix would be for colima to additionally bind to [::1] whenever it binds to 127.0.0.1 implicitly (same goes for [::] when the implicit binding is to 0.0.0.0).

acuteaura · 2023-03-20T08:33:56Z

I'm using colima to run a VPN alongside a socks5 server, and it looks like I need to remove IPv6 addresses and routes from my config files.

docker run -v (pwd)/<wg config with v6>.conf:/etc/wireguard/vpn.conf --cap-add=NET_ADMIN --rm local/wgd:latest
[#] ip link add vpn type wireguard
[#] wg setconf vpn /dev/fd/63
[#] ip -4 address add 10.66.140.107/32 dev vpn
[#] ip -6 address add fc00:bbbb:bbbb:bb01::3:8c6a/128 dev vpn
RTNETLINK answers: Permission denied
[#] ip link delete dev vpn

abiosoft · 2023-03-20T15:25:38Z

Maybe related: lima-vm/lima#1330

Yeah it is. Ipv6 is not properly supported in Lima yet.

genki · 2023-03-23T15:21:47Z

Facing similar issue.
Is there a way to disable IPv6 and use only IPv4?

So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.)

* proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (#1318) * add slurs to reserved words (#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (#1319) * Refactor appview repo subscription for memleak (#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]>

So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.)

* proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (#1318) * add slurs to reserved words (#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (#1319) * Refactor appview repo subscription for memleak (#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]>

* refactor appview services * tidy types * Allow moderators to take and reverse actor takedowns (#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (#1355) patch up a couple sqlite tests * Increase appview keepalive (#1360) increase keepalive to 90s * Appview - serve feed skeletons (#1265) * proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (#1318) * add slurs to reserved words (#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (#1319) * Refactor appview repo subscription for memleak (#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]> * add optional ilike query to getPopularFeedGenerators * fix lint * fix lint * handle sqlite too in pds only * fix lint * v0.4.3 * Include takendown posts for admins (feature branch) (#1361) * 🚧 WIP including takendown posts on author feed * ✨ Add takedown id on posts when including taken down posts * 🧹 Cleanup the auth verifier and other bsky package code * ✅ Add test for admin getAuthorFeed * 🧹 Cleanup lexicon and exclude takedownId * more explicit plumbing for post hydration w/o requester or with takedown info * pass along flag for soft-deleted actors * cleanup getAuthorFeed w/ auth * reorg getAuthorFeed logic around role/access-based auth --------- Co-authored-by: Foysal Ahamed <[email protected]> * ✨ Disable signing up with invite code from takendown account (#1350) * fix viewer data --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Eric Bailey <[email protected]>

earcherc · 2023-08-28T18:53:50Z

bump

So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.)

* proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (bluesky-social#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (bluesky-social#1318) * add slurs to reserved words (bluesky-social#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (bluesky-social#1319) * Refactor appview repo subscription for memleak (bluesky-social#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (bluesky-social#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (bluesky-social#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (bluesky-social#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (bluesky-social#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (bluesky-social#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (bluesky-social#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (bluesky-social#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (bluesky-social#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (bluesky-social#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (bluesky-social#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]>

* refactor appview services * tidy types * Allow moderators to take and reverse actor takedowns (bluesky-social#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (bluesky-social#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (bluesky-social#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (bluesky-social#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (bluesky-social#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (bluesky-social#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (bluesky-social#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (bluesky-social#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (bluesky-social#1355) patch up a couple sqlite tests * Increase appview keepalive (bluesky-social#1360) increase keepalive to 90s * Appview - serve feed skeletons (bluesky-social#1265) * proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (bluesky-social#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (bluesky-social#1318) * add slurs to reserved words (bluesky-social#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (bluesky-social#1319) * Refactor appview repo subscription for memleak (bluesky-social#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (bluesky-social#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (bluesky-social#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (bluesky-social#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (bluesky-social#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (bluesky-social#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (bluesky-social#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (bluesky-social#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (bluesky-social#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (bluesky-social#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (bluesky-social#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]> * add optional ilike query to getPopularFeedGenerators * fix lint * fix lint * handle sqlite too in pds only * fix lint * v0.4.3 * Include takendown posts for admins (feature branch) (bluesky-social#1361) * 🚧 WIP including takendown posts on author feed * ✨ Add takedown id on posts when including taken down posts * 🧹 Cleanup the auth verifier and other bsky package code * ✅ Add test for admin getAuthorFeed * 🧹 Cleanup lexicon and exclude takedownId * more explicit plumbing for post hydration w/o requester or with takedown info * pass along flag for soft-deleted actors * cleanup getAuthorFeed w/ auth * reorg getAuthorFeed logic around role/access-based auth --------- Co-authored-by: Foysal Ahamed <[email protected]> * ✨ Disable signing up with invite code from takendown account (bluesky-social#1350) * fix viewer data --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Eric Bailey <[email protected]>

So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.)

* proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (bluesky-social#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (bluesky-social#1318) * add slurs to reserved words (bluesky-social#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (bluesky-social#1319) * Refactor appview repo subscription for memleak (bluesky-social#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (bluesky-social#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (bluesky-social#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (bluesky-social#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (bluesky-social#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (bluesky-social#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (bluesky-social#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (bluesky-social#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (bluesky-social#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (bluesky-social#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (bluesky-social#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]>

* refactor appview services * tidy types * Allow moderators to take and reverse actor takedowns (bluesky-social#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (bluesky-social#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (bluesky-social#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (bluesky-social#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (bluesky-social#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (bluesky-social#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (bluesky-social#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (bluesky-social#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (bluesky-social#1355) patch up a couple sqlite tests * Increase appview keepalive (bluesky-social#1360) increase keepalive to 90s * Appview - serve feed skeletons (bluesky-social#1265) * proxy timeline skeleton construction to appview * add getFeedSkeleton to appview * mount route * smart proxy feed skeletons * tests * proper error code * only proxy specific feeds * build branch * update proxyable feed logic, should use feed publisher rather than generator * fix feed proxy tests, configure feed publisher (in addition to generator) * hotfix: prevent user-supplied rkey on posts with createRecord (bluesky-social#1313) * prevent user-supplied rkey on posts with createRecord * allow empty-string rkey parameter Co-authored-by: devin ivy <[email protected]> --------- Co-authored-by: devin ivy <[email protected]> * add slurs to reserved words (bluesky-social#1318) * add slurs to reserved words (bluesky-social#1314) * Update reserved.ts Add slurs to reserved words * Update reserved.ts fix typo * Update reserved.ts to clean up the slur list * linting * pluralise --------- Co-authored-by: jess <[email protected]> * identifier: tweaks and additions to slur list (bluesky-social#1319) * Refactor appview repo subscription for memleak (bluesky-social#1308) * refactor to remove closure in loop * move consecutive item out of p-queue * Handle validation improvements (bluesky-social#1336) * Handle matches and false positives for unacceptable words in handles * move handle validation logic to pds * missed merge * add cfg flag * encode lists * fix build issues * move words to cfg * tidy --------- Co-authored-by: Jaz Volpert <[email protected]> * Allow moderators to take and reverse actor takedowns (bluesky-social#1330) allow moderators to take and reverse actor takedowns * ✨ Allow searching reports by moderator did (bluesky-social#1283) * ✨ Allow searching reports by moderator did * ✅ Remove .only flags on tests * ✅ Update snapshot * ✅ Add checks for did match in actions * v0.4.1 * Make sequencer leader behavior optional on pds (bluesky-social#1250) * make sequencer leader behavior optional on pds * tidy * use 127.0.0.1 in with-test-db.sh for colima (bluesky-social#1297) So, since Docker Desktop has licensing issues, some folks use colima for running containers on their macOS machines (The licensing exempted CLI-only version of Docker only exists on Linux). Unfortunately, colima binds host ports only on the IPv4 localhost address (`127.0.0.1`) while the atproto postgres clients will attempt to connect to the IPv6 localhost address (`::1`) that macOS sets in /etc/hosts. See abiosoft/colima#583 and lima-vm/lima#1330 for the tickets against colima. (Docker Desktop binds to both IPv4 and IPv6 localhost addresses and so doesn't have this issue.) To workaround this silly issue, we can use `localhost` within the docker containers and docker-compose, but need to set the `DB_POSTGRES_URL` env var to use the IPv4 localhost explicitly. (Asking folks to edit /etc/hosts causes other tools to break and will be overridden on each OS upgrade.) * Subscription util tests (bluesky-social#1295) * consecutive list tests * flesh out subscription util tests --------- Co-authored-by: Devin Ivy <[email protected]> * Content reporting on record fields (bluesky-social#1351) * content reporting on record fields * fix test * tests * tidy * Check rkey contents just for non-tids (bluesky-social#1353) check rkey content for non-tids * ✨ Added new procedure for sending admin email (bluesky-social#1312) * 🚧 Added new lexicon for sending admin email * ✨ Add moderation mailer * ✨ Switch to text email content from html * 🧹 Cleanup some early implementation code and reflect PR reivew * ✨ Use smtp host instead of gmail service config * ✨ Move to using single smtp url * v0.4.2 * Patch up a couple sqlite tests (bluesky-social#1355) patch up a couple sqlite tests * enable feeds & build branch * disable branch building & enable without proxy header --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]> * add optional ilike query to getPopularFeedGenerators * fix lint * fix lint * handle sqlite too in pds only * fix lint * v0.4.3 * Include takendown posts for admins (feature branch) (bluesky-social#1361) * 🚧 WIP including takendown posts on author feed * ✨ Add takedown id on posts when including taken down posts * 🧹 Cleanup the auth verifier and other bsky package code * ✅ Add test for admin getAuthorFeed * 🧹 Cleanup lexicon and exclude takedownId * more explicit plumbing for post hydration w/o requester or with takedown info * pass along flag for soft-deleted actors * cleanup getAuthorFeed w/ auth * reorg getAuthorFeed logic around role/access-based auth --------- Co-authored-by: Foysal Ahamed <[email protected]> * ✨ Disable signing up with invite code from takendown account (bluesky-social#1350) * fix viewer data --------- Co-authored-by: Devin Ivy <[email protected]> Co-authored-by: Foysal Ahamed <[email protected]> Co-authored-by: Jeff Hodges <[email protected]> Co-authored-by: David Buchanan <[email protected]> Co-authored-by: jess <[email protected]> Co-authored-by: bnewbold <[email protected]> Co-authored-by: Jaz Volpert <[email protected]> Co-authored-by: Eric Bailey <[email protected]>

henrik242 mentioned this issue Jan 30, 2023

[Bug] Failed to connect to Reaper from 9.0.1 testcontainers/testcontainers-node#439

Closed

cristianrgreco mentioned this issue Mar 13, 2023

Fix issue with DOCKER_HOST and add limited Podman CI workflow testcontainers/testcontainers-node#494

Merged

cristianrgreco mentioned this issue Apr 19, 2023

Add support for Colima testcontainers/testcontainers-node#531

Closed

evanjd mentioned this issue May 10, 2023

Cannot use SDK v3 with dynamodb local - nodejs v18 aws/aws-sdk-js-v3#4294

Open

3 tasks

mlieberman85 mentioned this issue May 25, 2023

[bug] GUAC issues with ipv6 running docker compose on Colima guacsec/guac#888

Open

jmhodges mentioned this issue Jul 7, 2023

use 127.0.0.1 in with-test-db.sh for colima bluesky-social/atproto#1297

Merged

kaihendry mentioned this issue Aug 16, 2023

ci: smoke test on manager, bypassing envoy thoughtworks/maeve-csms#14

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

IPv6 localhost not supported #583

IPv6 localhost not supported #583

ujwal-setlur commented Jan 15, 2023

henrik242 commented Jan 30, 2023 •

edited

Loading

henrik242 commented Jan 30, 2023

shlomioz commented Feb 12, 2023

mxngls commented Feb 24, 2023

sabberworm commented Mar 9, 2023 •

edited

Loading

acuteaura commented Mar 20, 2023

abiosoft commented Mar 20, 2023

genki commented Mar 23, 2023

earcherc commented Aug 28, 2023

IPv6 localhost not supported #583

IPv6 localhost not supported #583

Comments

ujwal-setlur commented Jan 15, 2023

Description

Version

Operating System

Output of colima status

Reproduction Steps

Expected behaviour

Additional context

henrik242 commented Jan 30, 2023 • edited Loading

henrik242 commented Jan 30, 2023

shlomioz commented Feb 12, 2023

mxngls commented Feb 24, 2023

sabberworm commented Mar 9, 2023 • edited Loading

acuteaura commented Mar 20, 2023

abiosoft commented Mar 20, 2023

genki commented Mar 23, 2023

earcherc commented Aug 28, 2023

Output of `colima status`

henrik242 commented Jan 30, 2023 •

edited

Loading

sabberworm commented Mar 9, 2023 •

edited

Loading