Containers-roadmap: [Fargate] [bug/regression]: Modifying /etc/hosts does not work with 1.4.0 anymore

Created on 11 May 2020  路  2Comments  路  Source: aws/containers-roadmap

It used to be possible with Fargate 1.3.0 to add entries to /etc/hosts. With 1.4.0 I get the following error:

/usr/local/bin/entrypoint.sh: line 11: /etc/hosts: Read-only file system

This is unfortunately crucial as extraHosts via task-definition is not supported with awsvpc.

Fargate Fargate PV1.4
Source
picture lifeofguenter
👍8

Most helpful comment

This issue is now fixed and you should be able to modify /etc/hosts, /etc/hostname, and /etc/resolv.conf with PV 1.4

picture SaloniSonpal on 29 May 2020
❤3

All 2 comments

I need this fixed too or I have to abandon Fargate altogether. 1.3 doesn't work because I need EFS. 1.4 doesn't work because I need the flexibility to hack the /etc/hosts and don't want to do a workaround like instantiating BIND or some other DNS solution.

aberezin picture aberezin on 15 May 2020

This issue is now fixed and you should be able to modify /etc/hosts, /etc/hostname, and /etc/resolv.conf with PV 1.4

SaloniSonpal picture SaloniSonpal on 29 May 2020
❤3
Was this page helpful?
0 / 5 - 0 ratings

Related issues

tabern picture tabern  路  3Comments
yinshiua picture yinshiua  路  3Comments
miztch picture miztch  路  3Comments
talawahtech picture talawahtech  路  3Comments
clareliguori picture clareliguori  路  3Comments