Stefano Marinelli on Nostr: Something strange happened to me today. A developer reached out because after ...
Something strange happened to me today. A developer reached out because after restarting some #docker containers, nginx seemed to be behaving oddly. I connected and realized something big was off. It appeared to be a different container, bloated, and nginx wasn't even starting. After ruling out the possibility of the nginx image from the docker registry being compromised, we started to brainstorm. Long story short, another developer had created a custom image and named it "nginx," so the dockerfile was pulling it directly from the local setup... #DockerTroubles #Linux #Containers
Published at
2023-08-31 20:36:42Event JSON
{
"id": "5dbe2ebc70c14324553334a3ce4ca483f4589319aacf97f8d0e31e4103e3e9c7",
"pubkey": "ae3bf73746446a5edd319cef72033b539598a21ad07c2c2c4a84fbeaf22b835a",
"created_at": 1693514202,
"kind": 1,
"tags": [
[
"t",
"docker"
],
[
"t",
"dockertroubles"
],
[
"t",
"linux"
],
[
"t",
"containers"
],
[
"proxy",
"https://mastodon.bsd.cafe/users/stefano/statuses/110986146752516502",
"activitypub"
]
],
"content": "Something strange happened to me today. A developer reached out because after restarting some #docker containers, nginx seemed to be behaving oddly. I connected and realized something big was off. It appeared to be a different container, bloated, and nginx wasn't even starting. After ruling out the possibility of the nginx image from the docker registry being compromised, we started to brainstorm. Long story short, another developer had created a custom image and named it \"nginx,\" so the dockerfile was pulling it directly from the local setup... #DockerTroubles #Linux #Containers",
"sig": "5b1816db79bb5ccb5d24e2870210b11b19091668528efd4dc0ec74361566ce71eac25f0e973816a0d8a01c2f13ee0383c08a1f2c4e9a371361d823172399bc6b"
}
